• Resolved adamsen

    (@adamsen)


    I have version 3.2.1 installed on a fresh WP 2.7.1-installation without any other plugins activated. The blog is installed in a subdomain, and the plugin directory is symlinked. The directory structure is the usual, and a wp-config.php is found where plugins suppose to find it.

    Nevertheless, I keep getting this message: “eShop 3.2.1 is now ready to use. You must now deactivate and re-activate the plugin.” I can deactivate it, but when I activate it, I get a blank screen. The adress line says: http://test4.blogos.dk/wp-admin/plugins.php?action=activate&plugin=eshop%2Feshop.php&_wpnonce=xxxxxxxxx.

    Any suggestions?

Viewing 6 replies - 1 through 6 (of 6 total)
  • When eShop is first activated it creates some directories, and rechecks those when you re-activate things – so I’m guessing that that is where the problem lies.

    So can you check the existence of these directories:
    wp-content/eshop_downloads
    &
    wp-content/uploads/eshop_files

    files are then copied to these directories from 2 directories with in the plugin, eshop/downloads/ and eshop/files. (images from paypal, payson and cash are also transferred to the files directory).

    I’ve never moved directories elsewhere, so that may be causing a problem, but I can’t say for sure.

    the upload directory is found by using a native WP call, wp_upload_dir(). The plugin directory is found by the constant WP_PLUGIN_DIR.

    Thread Starter adamsen

    (@adamsen)

    The eshop_downloads and uploads/eshop-files directories did not exist. The plugin was not allowed to create them.

    By the way, the plugin directory is not symlinked, as I wrote. I do have symlinked plugin directories, but not on this blog.

    WP was told to use wp-content/uploads, but it didn’t exist, and WP 2.7.x neither created it nor told me that it wasn’t created.

    I would suggest that the plugin checks whether it will be able to create those directories and tell the user if one must do it manually. 🙂

    As for me, my problem is solved!

    Thank you!

    actually it is supposed to ‘die’ if those directories cannot be created. I’ve found it very difficult to actually test for the problem though as in all cases it always works for me straight away.

    I did move over to using more native WP functions to create the directories, in the hopes that they would work better, looks like I’m still out of luck 🙁

    But I’m glad it is now working for you.

    NHL23

    (@nhl23)

    I get this too, made the directories and have manually deactivated/activated and it still appears…

    And maybe i’m just dumb, but how do you create products to sell lol.

    elfin

    (@elfin)

    this topic/thread is resolved – please start a new topic/thread.

    I had this same problem while trying to activate eShop 4.3.1. with WP 2.9.1. Reading the above posts gave me the answer that files were probably not being written by the “activate” process. So, I temporarily set my wp-content dir permissions to 777, then Deactivated and re-Activated the eShop plugin. That did the trick!

    As Adamsen said above, it would be nice if the plugin stated this like many other plugins do when needing permission changes, either live or in the readme.txt file.

    Thanks Adamsen and elfin!

Viewing 6 replies - 1 through 6 (of 6 total)
  • The topic ‘Request for reactivation – eShop 3.2.1’ is closed to new replies.