Forum Replies Created

Viewing 4 replies - 1 through 4 (of 4 total)
  • Thread Starter abhempire

    (@abhempire)

    Thank you, my theme was a bit modified, i had an extra line of code in single.php which added an extra field. Removing that solved the problem and now the script works beautifully.

    Thanks for the patience, Paul!

    Thread Starter abhempire

    (@abhempire)

    You understood me wrong, i don’t want to send out emails. I just want the plugin to save them in a text file. User inputs his email, hits subscribe, email gets saved in a text file.

    Thread Starter abhempire

    (@abhempire)

    “The “fb-root” div has not been created, auto-creating

    all.js (line 52)

    Given URL is not allowed by the Application configuration.: One or more of the given URLs is not allowed by the App’s settings. It must match the Website URL or Canvas URL, or the domain must be a subdomain of one of the App’s domains.” – here i get an authentification error from facebook.

    I believe it’s from your App ID, but it should still work, right?
    So i just made an App and replaced the ID, second error went away.
    But that wasn’t the problem, because i still don’t see the buttons. Must be the first error in all.js

    If you want the link just let me know how i can send it to you without posting it here for everyone to see.

    Thread Starter abhempire

    (@abhempire)

    I managed to figure out why i was getting two separate errors on two different websites while the plugin was working ok on others.

    In the wp-config.php where you get the code

    define( 'WPCACHEHOME', '/PATH/wp-content/plugins/wp-super-cache/' ); //Added by WP-Cache Manager

    The actual line of code the plugin writes on installation is:

    define( 'WPCACHEHOME', ' /PATH/wp-content/plugins/wp-super-cache/' ); //Added by WP-Cache Manager

    If you look closely at the two lines you’ll see a small detail that seems to break the path to wp-super-cache, it’s an empty space in this place: ‘ /PATH
    That’s why some people had success activating the plugin after reinstallation, because sometimes it skips the empty space and writes: ‘/PATH

    How come no one figured this out till now!?

    After figuring out the problem on my first website, which was getting around 5 erorrs, i went to my second one which was getting some exec() error, closed the gap and the error was gone.

    Right now, i believe close to every path error people have comes from that gap in the code.

    Maybe you shold write this in the FAQ if you can’t fix it.

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