Kevin Cristiano

Sure:

WP 5.8.6

Have 1.22 installed with some blocks disabled (in my case many)

Upgrade Block Manager to 1.2.3

All Blocks are visible.

Clear caches: wp cache flush, server cache flush, restart apache, php, mysql

All blocks visible when you go to page add new. Choose blocks via keybord or any ‘plus’ symbol – same result.

Revert to 1.22:

Blocks show as expected

I have a small number of sites on 5.8 branch for some odd reasons.

Above is not an issue on WP 5.9

I can reproduce this issue on WP 5.8.x, 5.9+ is OK.

I don’t have anything in the php or apache error logs.

It’s the same issue – empty square is looking at the same dev site. He just ran a curl on the url, while I let WP handle it. WP returned a page not found for me, but the curl is finding the true error:

PHP Fatal error: Call to a member function format() on boolean in /home/vzendo/public_html/wp-content/plugins/event-organiser/templates/ical.php on line 61

It looks like we are failing on the timezone functions.

FYI – php 5.6.22, apache 2.4.10 and MySQL 5.6 on Debian

404 errors.

Thanks for the response. I did a rewrite flush (via cli and through permalinks) and no change.

Any other thoughts?

This is a link to a dev site I have to test this https://vzdev.tadpole.cc/calendar/

Thanks for posting this here.

Have you pushed an update to the theme yet?

Can you post an update here since you have pushed out a new version? It would be good to kn ow what you found — now that it has been corrected.

Thanks.

On sites that I have with SSL the non SSL (https://) urls all still resolve including https://example.com/feed.

Hi,

They changed the search results for 3.7. The results should now show more relevant posts near the top.

See Trac Ticket and 3.7 Release Notes

I would follow the instructions that the release post mentions: 3.5.1 for IIS

I agree it looks like the hotfix plugin has not been updated with this, but adding the code in Option 2 should work.

For the permalinks, I mean to go to example.com/wp-admin/options-permalink.php and verify the permalink settings there.

For timeouts the two timeouts that I look at in php.ini are:

max_execution_time = 30
max_input_time = 60

When I had a problem with the media upload function,it was a timeout. Try changing the number of items displayed on the library (set under help) and in the upload area, try the browser upload. If this allows you to work with media, I would think the issue is timeouts. I would not increase them much at all, as high values in those settings are not recommended.

I also use the wincache module on my IIS servers, That has a whole host of other issues now (which is why after many years on IIS I have moved most of my sites to a LAMP stack), but it does help load times even. I can not recommend it right now. I am running a dev build to keep it working with WordPress as the release version has issues with file locking (problem for automatic updates).

I agree that it is probably not the url rewrite module if only happens on one site.

One last thought, IIS had been trapping a WordPress wp_die call as a 500 error. I used to fight this one and finally told IIS to pass errors to the application first before responding.
To do this add to your web.config:

<system.webServer>
<httpErrors existingResponse="PassThrough" />
... all your other stuff
</system.webServer>

If none of the above is applicable, can you give us a link to the site with errors? There must be something in the url that is causing IIS to error out.

What version of url rewrite are you running? Can you post (pastebin) your web.config entries related to the rewrite rules.

I have had issues with media.php when there were too many images and I hit a php timeout.

I would also verify your permalink settings if you have not done that yet.

BTW, did you meand WordPress 3.1.3 or 3.3.1?

I misspoke above, the publishing issue is not limited to IIS, but also occurs on Apache on Windows Servers.

Not sure of the best way to do this, so I created a ticked on the plugins trac. The ticket includes the chages that worked for me.

@lapommecroquee Are you by any chance on a Windows (IIS) Server?

I noted a problem with automatic publishing due to (what seems) a problem in the php curl library for php for windows only.

I was able to get SFC 1.0 and 1.1 to connect and publish by changing 3 files. I believe this is an error specific to IIS. Once I am back where I can access the files I will make the diff file available to Otto.

I have not done 3.2.1 on IIS 5. I did (I think) WordPress 2.0 on IIS 5, but that was ages ago and just not worth it. I do not even have an instance of IIS 5 to test on any more.

From the steps you have done already, I am at the end of my ideas. You do say you have tried different browsers. Which and have you completely dumped the cache (of the browser) and then tried?