Boldt

Follow-up: After looking at the code I’m guessing that making your front end css dependent on wp-editor causes the problem. I edited init.php to remove the dependency in the front end and the problem disappeared.

Seems to be!

We need an added CSS style that adds a large z-index to block toolbars.

Yeah, I played around with that approach for a bit, but I couldn’t get it to work before I had to get on to something more urgent.

I was mainly hoping that I was missing something obvious that other people were using. Oh well.

OK, got it. Perhaps add an option to clear the localstorage?

Found the problem. Once I cleared cookies for the website it started working. I’d only tried clearing the cached data previously. Not sure which cookie it was, but it’s fixed now. Does SG Optimizer set any site cookies that might be causing that problem?

If it happens again I’ll take a look at the cookies in more detail before clearing them.

The topic is resolved because it’s not a plugin issue.

You closed it before I could even give you the info you asked for! You didn’t know whether my issue was the same as the other guy’s. From my perspective, when you closed the topic you slammed the door on me getting any help. I’m going to have to reconsider recommending Siteground to my clients if this is the kind of support they’ll get.

I am afraid not. I can’t troubleshoot your browser or unknown websites. I am marking this as solved because that’s something with your particular installation and not a general plugin issue.

I opened this topic before I went to bed last night and you closed it based on someone else’s comments before I woke up this morning. Good job.

Resolved? Definitely not.

I can confirm that it only happens in Google Chrome. It doesn’t occur in Firefox or Safari.

Tobias,

Thanks for the quick reply. Yes, the table has a #colspan#. I didn’t think about that as a possible explanation.

You’re welcome.

It’s probably because of the parameter to the function get_intermediate_image_sizes () called on line 109. Since the function doesn’t actually take a parameter you can delete the “$post->ID” parameter and likely eliminate the notice. You can remove it from the call on line 19, too.

Still broken in 2.5.18. It looks like it’s a problem with local/GMT time.

BTW, I originally reported this 9 months ago here.

• This reply was modified 7 years, 8 months ago by Boldt. Reason: Added my original report of this error

Thanks, and no trouble. Great plugin. I started digging into the code and found that filter. I was going to try it out but you saved me the time.

If anybody is experiencing the problem with the next month link in month view like the original poster on this topic I posted a description of the bug and its solution to this support forum on 26 June.