Forum Replies Created

Viewing 6 replies - 1 through 6 (of 6 total)
  • Thread Starter Semetery

    (@semetery)

    Thanks! ??

    All I was told was that there were invalid lines added to my config file and that caused me the HTTP errors. I wish I could be more helpful but I thank you for your time and the plugin, it is highly recommended by my host.

    EDIT: I reinstalled and now, for whatever reason, it works fine. I don’t know what the difference is honestly but it’s working great!

    • This reply was modified 8 years, 2 months ago by Semetery.
    Thread Starter Semetery

    (@semetery)

    My server admin found and removed the issues below:

    PHP Parse error: syntax error, unexpected ‘;’, expecting ‘,’ or ‘)’ in /home/site/public_html/wp-config.php on line 56
    PHP Parse error: syntax error, unexpected ‘;’, expecting ‘,’ or ‘)’ in /home/site/public_html/wp-config.php on line 56

    I apologize if that’s not related to the plugin but the last thing I did was activate it. Either way, it’s working again now that those problems were fixed.

    Thread Starter Semetery

    (@semetery)

    Anyone have any idea what with W3 could be causing the issue?

    I’ve switched to WP Faster Cache and haven’t had any of the problems at all but, personally, my site seemed to load a bit faster with W3.

    Thread Starter Semetery

    (@semetery)

    Sorry to update so soon but I copied the post into a NEW post, saved and then tried to share and it worked properly. Could W3 Total Cache have something to do with that?

    I’m still only getting ‘Share on Facebook,Twitter,Google+’ as the descriptions but that’s another issue.

    I noticed this too. I use CloudFlare and was wondering where the support for it went?

    I read in another post that there were apparently issues with it? Is it coming back?

    Thread Starter Semetery

    (@semetery)

    The site is on my local server currently, but here is a screenshot:

    https://imageshack.us/photo/my-images/820/screensou.jpg/

    You’ll see that the placement is up in the header for some reason. It’s ONLY in Internet Explorer 8, works perfect in all other browsers I’ve tried including mobile.

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