rajupp

This has not been resolved properly. It’s still injecting hidden image to WP core at a different place

Ok, I figured out the issue.

single.php under “themes”->”default” has “Article Headline” hardcoded instead of fetching the title.

On line number 109, changing “Article Headline” to “<?php echo the_title(); ?>” resolves the issue. I’m surprised how the developers missed this.
Now got to wait for Google to crawl all those indexed pages and get the proper title. Sigh.

• This reply was modified 8 years, 6 months ago by rajupp.

Yes, this is happening for me as well. There is no solution?

Sorry, it still doesn’t work for me. Anything else to change than what you have mentioned?

Thank you! But now YouTube is showing 0. I even tried creating new project and API key

It’s been a week and there have been multiple threads with same/similar issue. Any solution expected?

When can we expect the next release Frederick? I’m sure you have lots of new features and bug fixes in store for us!

Is it even possible to choose anything other than Disk? Other options are greyed out for me

Thanks. But the issue persists. I checked my .htaccess and wp-config.php files. both of them are unchanged and don’t contain any of the entries as described in the post.
Database has 2 tables related to BWS and both of them are empty. I don’t understand which file/code is calling the …/better-wp-security/inc/filecheck.php which results in the above error. Any pointers?

any official take on this Frederick?

Issue is more than 9 months old and not fixed officially yet? I still get these errors. I hope the fix mentioned above is the right one

Thanks Mangesh,
With my limited ability to play with codes and consoles, I found that my theme has some hardcoded references to jquery ui, but couldn’t fix it. I had to Hide WordPress SEO box on edit post pages. Dirty fix, but works

It would be great if you can let me know how you fixed it. How to know which plugin is clashing with WordPress SEO and then how to make it use jQuery UI 1.8.16?

Wonder why this issue isn’t fixed as yet? Any progress with the support tickets filed by people above?

any way to get back v2.3?