Installing to Subdomain – unexpected results

Wow I have never heard of that happening with the extraction outside the give directory. The code for that routine uses ZipArchive::extractTo Which only allows 1 destination path. So I’m thinking a few things could possibly be at play:

1. The root director actually was set as “\public_html\” You can double check this value by opening the “System Requirements” button on step one of the installer.

2. If it was actually set to \public_html\distributor\ then you may have your sub-domain mapped to \public_html\ via your c-panel setup or you might possibly have a symbolic link that maps “\public_html\distributor\” back up to \public_html\

However to say that some got extracted to one location and others got extracted to another location seems strange and would be a serious issue within the core PHP zip library, which has been used on millions of systems and never had a bug report created for extracting the package to simultaneous directories.

Will investigate further – here’s the system requirements :

REQUIREMENTS click links for details
Root DirectoryPass
Path: /home/vikuzpuz/public_html/distributor
[Pass] Is Writable by PHP
[Pass] Contains only one zip file
Result = 51f60ecb00d7f7635_20130729_knotlace_package.zip
Note: Manual extraction still requires the package.zip file

Further checking – I jumped to the wrong conclusion or something different happened. I cleared out all content from subdomain (except for the installer and package) and from the normal domain and ran the installer.

All unpacking happened into the subdomain. Still received the same error for that plugin (social locker). Cleared it all out again and ran again, this time de-selecting the social locker plug-in activation and it seems to work fine.

Not sure what went wrong yesterday. Also not sure why that specific plugin causes the php error – seems like its still referring to the old address :

Warning: include_once(/home/knotlace/public_html/wp-content/plugins/sociallocker/items/activation.php) [function.include-once]: failed to open stream: No such file or directory in /home/vikuzpuz/public_html/distributor/wp-content/plugins/sociallocker/libs/factory/layouts/loader/loader.class.php on line 268

Hi ejlees,

Thanks for posting your update! You might do a compare before and after:

1. Go to the site where social-locker works and check all the plugins files, or just do a count of the files
2. Then go to your new duplicated site and do the same and see if the file counts match

If that plugin had any files with a name over 260 characters or the permissions are too restrictive then some of the files may have not been packaged. If the file count is the same then you might check with the theme authors and see if they can help you pin-point the issue..

Cheers~