Re: OpenImporter
Reply #54 –
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.
ETA: package removed.
Re: OpenImporter
Reply #55 –
phar-out baby, I'm going to give it a try !
I should have mentioned that after you create your abstract class then your tests extend that instead of extends PHPUnit_Framework_TestCase so myTest extends OpenImp yada yada ... Just a way to call those before and after things at the top level of each test class.
Re: OpenImporter
Reply #58 –
I did not change anything, the files are the same that I sent you.
where should I put the php file? in the root of my smf forum? Itried but I see a blank page