Skip to main content
Topic: OpenImporter (Read 59472 times) previous topic - next topic
0 Members and 2 Guests are viewing this topic.

Re: OpenImporter

Reply #60

thank you for your support but I'm still having this

Code: [Select]
mporting settings... ✔
Importing members... ✔
Importing attachments...

( ! ) Fatal error: Maximum function nesting level of '100' reached, aborting! in C:\wamp\www\importer\OpenImporter\Utils.php on line 88
Call Stack
# Time Memory Function Location
1 0.0007 728920 {main}( ) ..\import.php:0
2 1.1266 2292568 ImportManager->process( ) ..\import.php:69
3 1.1268 2293704 call_user_func ( ) ..\ImportManager.php:236
4 1.1268 2293704 ImportManager->doStep1( ) ..\ImportManager.php:236
5 1.2028 2460976 Importer->doStep1( ) ..\ImportManager.php:465
6 2.2083 2475040 XmlProcessor->processSteps( ) ..\Importer.php:516
7 2.2190 2476616 XmlProcessor->doSql( ) ..\XmlProcessor.php:99
8 2.2233 2546024 XmlProcessor->prepareRow( ) ..\XmlProcessor.php:157
9 2.2234 2545160 eval( ' moveAttachment($row, $this->db, $this->config->from_prefix, $this->step1_importer->getAttachDir($row)); ' ) ..\XmlProcessor.php:212
10 2.2239 2545160 moveAttachment( ) ..\XmlProcessor.php(212) : eval()'d code:2
11 2.2241 2548752 copy_file( ) ..\smf2-0_importer.php:109
12 2.2241 2548960 create_folders_recursive( ) ..\Utils.php:58
sorry for my bad english

Re: OpenImporter

Reply #61

 emanuele needs a new brain to understand php on windows... :-[

Sorry, I'll test it tomorrow if I can manage to wake up my brain... :-[
Bugs creator.
Features destroyer.
Template killer.

Re: OpenImporter

Reply #62

take your time, there is no hurry for me, it's just a test in localhost  (under wamp on windows  O:-) )
sorry for my bad english

Re: OpenImporter

Reply #63

Maybe I got it: are you using the same installation of Elk that you used before in your tests?
If so, the attachments directory settings may be messed up and so when the importer tries to import the data fails. I realised just now while trying on an already messed up install.
Bugs creator.
Features destroyer.
Template killer.

Re: OpenImporter

Reply #64

Quote from: emanuele – And here it is an experiment.

Instructions:
unzip
upload
* point to import.php

That's an experiment to understand if it is worth exploring the route of the phar archive.
A phar archive is a "special" php file that includes the entire application into a single file (actually it needs two: the phar and a php to run the phar, meh). I thought this may be easier to handle for the "final users" in that specific case, since it would be a "one shot" and have lots of files and directories to deal with could be a little pain, while two files are much easier to track in the process. Also in theory the released package doesn't require any change to the files, etc.

Anyway, I tried this solution, though reading around there are some configurations that do not like phar (e.g. suhosin) and if it doesn't work on the majority of systems, it may not be worth to maintain a double system of distribution (that would create confusion I think).

Let's see.
I tried this in a live site and everything was imported ;)
sorry for my bad english

Re: OpenImporter

Reply #65

Sounds like I have to check the data taken from the db as well to be sure are "valid".

It's difficult to draw the line where things can be trusted and where not, I guess the attachments directory is one of those that cannot be trusted 100%.
Bugs creator.
Features destroyer.
Template killer.

Re: OpenImporter

Reply #66

attachments, avatars and custom fields were imported. I'll check the rest later ;)
sorry for my bad english

Re: OpenImporter

Reply #67

Sounds great!  :)


Re: OpenImporter

Reply #69

Ah very cool !

We do have sensiolabs_security_checker: true as part of  our scrutinizer.yaml file but I don't think that check is as complete as the running it there !

OK now get rid of all those globals :D

Re: OpenImporter

Reply #70

I tried with Elk, but it was not able to finish... xD
Bugs creator.
Features destroyer.
Template killer.

Re: OpenImporter

Reply #71

Is the importer nearly perfect now? ;)

I want to try to migrate soon but I am not sure which fixes I have to make to the importer. Or is the package up to date?

Re: OpenImporter

Reply #72

"Perfect" is a difficult word. lol

It should work for most of the things (including attachments).
Improvements are always possible. ;)
Bugs creator.
Features destroyer.
Template killer.

Re: OpenImporter

Reply #73

Difficult? No... Try it!

P - e - r - f - e - c - aaaaand finally - t !

So easy!  :D

Re: OpenImporter

Reply #74

ROFLMAO!
Bugs creator.
Features destroyer.
Template killer.