SomethingWonderful
Forum Replies Created
-
Updating Event-On Calendar fixed the outstanding issues with Chrome too.
Although the process is a complete crapfest….
Good for you sh-themes.
Had a few Woo problems.
I have also found Event-On Calendar plugin buggers up Chrome too. Disabling it fixed the Chrome issues…
Forum: Fixing WordPress
In reply to: 4.2.3 caused all my embedded forms to stop displayingHi Tara,
I think it’s more than just a compatibilty issue, I’m getting loads of issues on nearly 80 or so sites. Mainly WooCommerce sites but many different problems, and primarily on Chrome browsers…
Woo commerce maybe?
Update required….
Forum: Fixing WordPress
In reply to: 4.2.3 caused all my embedded forms to stop displayingLoads of issues on Chrome for me and others…
FF ok, Safari OK, IE ok. But I have multiple sites that are fried with Chrome and WP 4.2.3.
Could be an interesting day or so…
Forum: Fixing WordPress
In reply to: 4.2.3 caused all my embedded forms to stop displayingChrome?
I don’t think you can change core files by reverting back – WP need to provide a fix.
Yep Rifa – same here…
Amazed that WordPress let this happen… Here’s hoping to a quick fix…
Really don’t want to be rolling back WP on 200 sites….
Also having issues with websites and Chrome…
Images not showing, headers and footers broken, all gone a bit haywire…
Forum: Fixing WordPress
In reply to: Parse Error: Syntax Error when index.php copied to rootI RESOLVED this issue by using the file editor within cPanel and Extend on my two hosting accounts.
Whenever I tried to edit the code in text editor on my iMac or within Dreamweaver I would get the errors mentioned above. It was driving me mad..!!!!
As nicocluster says I think it’s an issue with text editor for mac.
Forum: Fixing WordPress
In reply to: Parse Error: Syntax Error when index.php copied to rootHi keesiemeijer,
TextEditor on Mac, but like I say, I’ve tried copying the index file from other working sites to no avail.
I think it might have something to do with
require( dirname( __FILE__ ) . ‘/path_to_wordpress_here/wp-blog-header.php’ );
which has just changed in the new version from
require(‘./wordpress/wp-blog-header.php’);
Hence the message
T_ENCAPSED_AND_WHITESPACE
SW
Forum: Fixing WordPress
In reply to: Parse Error: Syntax Error when index.php copied to rootHi again Esmi,
Have tried copying the file directly from a working site, no luck. Have also used Installatron to install WordPress files and DB and same problem.
I’ve also used exactly the same technique on over 100 WordPress sites in the last 3 years.
I’m asking the hosting company to look into it but they are denying any issue their end. I think I’m going to have to go to a new host but that is such a nuisance.
So frustrating…
SW
Forum: Fixing WordPress
In reply to: Parse Error: Syntax Error when index.php copied to rootHi Esmi,
That’s no different to what I have been doing? My apologies but I used the older WP index.php in my first answer to you then corrected a couple of posts down.
I have spoken to one other person who had this problem, using a different hosting company to me. He couldn’t find an answer either. But I can’t believe we’re the only two?
The only solution for me at the moment is to install wordpress in the root directory but that really isn’t ideal…
SW
Forum: Fixing WordPress
In reply to: Parse Error: Syntax Error when index.php copied to rootAhh no, just wanted to separate the code.