tag:wedge.org,2012-03-16:newsWedge - Importing into Wedge2024-03-19T02:19:18ZLive information from Wedge
Wedge
WedgeImport large WBB to WedgeGODhttps://wedge.org/profile/GOD/2015-08-18T14:47:08Z2015-08-18T14:47:08Ztag:wedge.org,2015-08-18:topic-8795The importer fails at "step=1", with the following error:
Code: [Select]Message: set_time_limit(): Cannot set time limit due to system policy Trace: set_time_limit(): Cannot set time limit due to system policy Line: 1513 File: /<redacted path>/import.php
I'm guessing it is some sort of DB authorization that's missing, but I don't know enough about this stuff to know where to start looking. Would anyone care to enlighten me?]]>Leftiehttps://wedge.org/profile/Leftie/2014-05-06T22:00:16Z2014-05-06T22:00:16Ztag:wedge.org,2014-05-06:topic-8608Importer Problem Attachment not found [solved] SMF2.0 import my forum no errors import complate
but problem all attachments can not be downloaded can not be preview thumbnails
check attachments folder, directories no error regular..
All the files are on the list but can not be downloaded
File Maintenance
Attachment Integrity Check
and clisck "Continue" button "Browse Files" is empty :):( ]]>gevvhttps://wedge.org/profile/gevv/2014-04-11T22:17:53Z2014-04-12T17:05:46Ztag:wedge.org,2014-04-11:topic-8570SMF 2 to Wedge importer errors
Code: [Select]Importing settings... ✔ Importing members... Parse error: syntax error, unexpected T_DOUBLE_ARROW in /home/creedmoo/public_html/upgrade/import.php(743) : eval()'d code on line 8
Parse error: syntax error, unexpected T_DOUBLE_ARROW in /home/creedmoo/public_html/upgrade/import.php(743) : eval()'d code on line 8
All members and their info is listed for the values. After that I get.
Code: [Select]Unknown column 'new_pm' in 'field list'
]]>txcashttps://wedge.org/profile/txcas/2014-02-26T17:43:47Z2014-02-26T17:43:47Ztag:wedge.org,2014-02-26:topic-8481Importing member fields into members.data?@TE...
I'm looking into moving some {db_prefix}members columns into {db_prefix}members.data, where they'll be serialized and stored with other variables.
A few reasons for that... - Well, there are 60 or 70 columns in that table... Not exactly EASY to browser through. - I think I could save about a dozen (or at least half a dozen) columns by moving them to data. - Basically, anything that (1) doesn't have an associated index, (2) doesn't need to be updated for anyone but the current user.
For now, I've moved 'mod_prefs' to data['modset'], and 'secret_question/secret_answer' to an array called secret_qa. What I've been doing is: enter this into my new Upgrade script (not yet committed), where Wedge will get the existing entries, then convert them to data variables, and then remove the columns when it's done.
I guess it works fine if you're on a current install of Wedge: the upgrade script will pick it up, and then upgrade your table automatically. But what if you're installing a new version..? The upgrade script won't run, because the database is in the new format, and it doesn't need to run. So... What to do?
(a) Leave the database with all these extra fields, because it's only annoying when browsing through phpMyAdmin, but 10 less fields won't make a big difference in either convenience or performance. (I'm not saying it won't; I'm giving you an opportunity to say whether you think it will.)
(b) Leave the database as is, at Wedge install time. Also set the database version to zero, basically... And let Wedge process it. But this means the import process needs to be done immediately after installing. Ouch... (Because, otherwise, Wedge will then start the upgrade process, and then delete the columns after it's gotten zero results on secret_* etc.)
(c) Add some code in the import script to make it possible to easily import an member field into the members.data field.
What do you think, guys..? (Especially Thorsten!)]]>Naohttps://wedge.org/profile/Nao/2014-02-16T00:11:01Z2014-02-16T00:11:01Ztag:wedge.org,2014-02-16:topic-8451