Forum Replies Created

Viewing 6 replies - 1 through 6 (of 6 total)
  • Hi James,

    Thanks for the suggestion. Here’s the content:

    The error was:
    YOU DO NOT HAVE SUFFICIENT PERMISSIONS TO ACCESS THIS PAGE.

    As we migrate, we usually take the old database and do a few search and replace operations:
    1. check siteurl and replace the old url with the new one.
    2. search for “home” and find out what the absolute path is for the server environment. Replace the old path with the new (e.g., “home/acctname/public_html/” gets changed to “home/acctname/www.yourdomain.com/” in the case of lunarpages to dreampress).
    3. check wp-config in the old environment vs. new one for table prefix. In our case the old environment was “wp_” and the new environment’s table prefix was “wp_acctname_”. I did a search and replace and replaced ‘wp_ with ‘wp_acctname_

    After importing the new database, the web site looked great from the front end, but as soon as we tried to log into WordPress we got that dreaded message.

    After googling it, there were a bunch of suggestions we tried, such as:
    1. check the user’s wp_capabilities and make sure they don’t have the wrong type of quotes
    2. check the user’s wp_user_level
    3. look for corrupt tables in the db

    But none of those worked. In the end, it was an issue related to my step #3 that I didn’t do correctly. My new environment had that special table prefix, and I hadn’t done the search and replace properly.

    We had a look around and found the issue, and it relates to the various places the table prefix shows up in the database.

    THE DATABASE TABLE PREFIX IS NOT JUST USED IN THE DATABASE TABLE NAMES. IT’S ALSO USED IN DATA!

    If that data isn’t also changed, a permission error happens because the returned values will be empty.

    Specifically, these changes fixed the issue:

    In the table: wp_acctname_options
    there was an option named: wp_user_roles
    that had to be renamed to use the prefix: wp_acctname_user_roles

    And in table: wp_acctname_usermeta
    there was a meta_key: wp_capabilities
    that had to be renamed to use the prefix: wp_acctname_capabilities

    And there were some other meta_key names in the user_meta table that started with wp_ and were expecting the same treatment, so I changed those as well. But these 2 were the critical ones preventing logins from happening.

    After making those changes, the login worked again.

    Plugin Author trillamar

    (@trillamar)

    Hi Folks,
    We’re looking into this right away.

    Thanks for letting us know.

    Plugin Author trillamar

    (@trillamar)

    It appears that when trying to write to file, PHP on your server was denied from being able to write to the file output. This usually happens when the user that the web server and php process runs on is not granted write permission to the directories under the wp-content directory. The owner of the directory system is likely different as well.

    To correct the problem, you can do one of 2 things:
    1. Change the plugin settings to “serve dynamically” instead of “serve from cache”. That will remove the necessity for the plugin to write to your file system.

    2. Grant write access to the wp-content directory and all of its contents to the user that PHP and web server is operating under.

    We will fix the plugin so that a better error message is printed out in a future release.
    Thanks for reporting this to us.

    Plugin Author trillamar

    (@trillamar)

    Hello tesse_k and wallee,

    We recently had some issues like yours. We fixed it by unchecking the “preload videos” setting, i.e., don’t preload them. This was especially problematic on Safari.

    Also, are you using the latest version of the plugin?

    Most people have issues because their path to the directory isn’t right.

    Hope this helps.

    Lucinda

    Forum: Plugins
    In reply to: [AutoChimp] AutoChimp Error

    talk2bks,

    THANK YOU!

    Plugin Author trillamar

    (@trillamar)

    Hello Bruce,

    1. In your WordPress dashboard, go to Settings > Secure HTML5 Video Player and there is a space there to specify the location of the folder where your videos live.

    2. On the page or post where you want the video to appear, use a shortcode , e.g.:

    [video mp4="video_clip.mp4"]

    on that same admin page, there are examples of various shortcodes for the type of video you’re serving up.

    3. You don’t need a player. VideoJS and FlowPlayer are part of the code.

    Hope this clears things up. Good Luck.

    Lucinda

Viewing 6 replies - 1 through 6 (of 6 total)