dailyblogtips

I do not have any plugin that could cause the 500 error. The error is caused because the index.php file on that folder calls for WordPress functions that don’t exist when you try to access it directly, hence the 500 error.

Any clue how to fix it?

• This reply was modified 6 years, 3 months ago by dailyblogtips.
• This reply was modified 6 years, 3 months ago by dailyblogtips.

500 error is the normal WP behavior, isn’t it?

For example: https://techcrunch.com/wp-content/themes/techcrunch-2017/

So think I don’t need to fix that, but rather why Google is crawling that folder when it shouldn’t.

• This reply was modified 6 years, 3 months ago by dailyblogtips.

Thanks

All right I managed to fix this on all posts running the following MySQL query:

UPDATE wp_posts SET post_title = REPLACE( post_title, ‘”‘, ” );

Thanks

@kmessinger, thanks for that.

How do I fix it though (i.e., remove the amp)? Cause when I look at the WP editor, or directly at the MySQL database, all I see is the ” symbol on the title of that post.

Sure if it solves the problem I’ll mark the thread as resolved. Still testing it out though.

That might be a solution. I’ll test it out, thanks.

Found a fix. I manually typed mydomain.com/wp-admin/update-core.php and then re-installed WordPress from there. It solved the bug.

get_the_date(‘n’) solved the problem. I guess the query_posts function receives the month parameter without leading zeroes, so ‘M’ won’t work as it adds leading zeroes.

My code ended up like this:

$year = get_the_date('Y');
$monthnum = get_the_date('n');
query_posts( "year=$year&monthnum=$monthnum&posts_per_page=-1" );

get_the_date(‘Y’) worked perfectly for year. get_the_date(‘M’) didn’t work for month though. So right now when I load the archives of a single month it loads all the posts of that year.

I am investigating, and thanks for the help.

What happens when you put deepblue on, and try to leave comment?

Could be a coincidence, so you got test this.

you got use the “optional excerpt” field for that, and put the image tag there

What IE version?

The theme is supposed to be compatible with IE6 onwards.

Are you sure it is not an element you introduced that is causing that?