• Resolved brightgirl

    (@brightgirl)


    I recently migrated a site using Participants Database from one host to another. We are now getting errors in the Admin that the uploads directory is not writable and the plugin is unable to open the debugging log file. The errors say that both of these are located in /nas/content/live/a2pianoprod/wp-content/uploads/participants-database/, however that location does not exist on the new hosting server. /wp-content/uploads/participants-database/ exists and is writable and that’s what the File Upload Location is set to in the plugin settings. I’m not even sure where it is getting the /nas/content/live/a2pianoprod from? I searched the db for that and the only thing that came up was the actual error message from Participants Database. Why is the plugin looking for that and how can I fix it?

Viewing 5 replies - 1 through 5 (of 5 total)
  • Plugin Author rolandbarker

    (@rolandbarker)

    I’m sorry, I can only guess what is wrong there. The plugin gets the path to the content directory from the WP configuration, so if that is incorrect, it can’t be fixed in the plugin.

    Since you have migrated, there could be incorrect information in your wp-config.php file, which should be checked to make sure everything is correct in there. It is possible there are additions to that file that are specific to your previous install that should be removed. There is an excellent reference for editing the config file here: Editing wp-config.php

    Thread Starter brightgirl

    (@brightgirl)

    I checked the wp-config file and found that it was a WPEngine-specific config file. I followed WPEngine’s instructions on their website for migrating away from WPEngine and removed the directories they said to remove. I then replaced the config file with a standard wp-config and re-entered the database credentials. I was hopeful this would resolve the errors we are seeing in Participants Database but sadly it did not.

    After that, I reached out to my current host to have them review the new config file and also check for anything elsewhere (for example, htaccess) that might be redirecting the path for the entire site, but they could not find anything and said all was proper and as expected.

    I then double checked the plugin settings:
    File Upload Location is set to: uploads/participants-database/
    The box in Advanced Settings for File and Image Uploads Use WP Content Path IS checked
    And I then double checked the wp-content directory via FTP to make sure that upload location exists (it does).

    Is there anything else I can try to do to resolve these errors?

    Plugin Author rolandbarker

    (@rolandbarker)

    Since it sounds like you have everything configured correctly, did you try uploading a CSV file? (Ignoring the error message). If it works, the error message is incorrect (which happens in some cases) and use the “Don’t Show File Uploads Location Warning” setting to suppress it.

    The other thing to do since it sounds like you are using a standard WP directory structure is to uncheck “Use WP Content Path” and then change the location setting to the default wp-content/uploads/participants-database/

    Thread Starter brightgirl

    (@brightgirl)

    I had already tried your second suggestion (unchecking Use WP Content Path and changing location setting to the default), but that made no difference in the error messages.
    I now tried uploading a CSV file and it worked with no issue at all! So it appears in this case, the error messages are incorrect and I checked the box to suppress it. Still bothers me a bit that there are incorrect error messages being thrown, though. However, I guess since it works I’ll let it go and not worry about it further.

    Plugin Author rolandbarker

    (@rolandbarker)

    Yeah, it bothers me too! But this was the best solution I could come up with because this is a server configuration issue, I can’t solve it with a plugin. Thanks for posting that you got it working!

Viewing 5 replies - 1 through 5 (of 5 total)
  • You must be logged in to reply to this topic.