rl347

I too had this problem, but it has disappeared with WordPress 5.5.1, possibly with this item: “#50919 – Script Loader: Change the jquery handle back to an alias for jquery-core”

Now find it also sometimes happens in Nextgen; not sure of cause but clearly not Foo/Owl. Sorry for any unnecessary effort caused. Ron

Have abandoned use of plugin

Scott, Just discovered a similar problem on the dynamic site, seems to be caused by Wordfence (although not using their caching), but too soon to tell whether something else is involved. Anyway, temporarily disabling wordfence makes the originally reported problem on simply static disappear! Thx for responding. Thread closed

See https://www.dropbox.com/s/tfe0d38o85qw9hx/P1TorrAGE.zip?dl=0
(sorry for pagination)

Trying to think what is different. caching disabled. I have both foogallery and nextgen rabe version (1.8.3 from memory) – am just migrating from Next to Foo.

Ron

Matt, that is impressively fast response.

Sorry, in my testing, I left the gallery with two images. Took one out now and the problem reappears. Ron

I have solved this and I think I understand why.

I am stupid!

I am doing redirect in php code executed within wordpress page. It seems that headers have already been sent in this situation. On my development site, where I didn’t get ‘header sent’ I had enabled ‘WP Fastest Cache. On the operational Site I hadn’t. When I enabled it the problem went. Presumably the cache prog adds in that stuff later.

(mind you when I tried the same with a different cache program the problem remained; maybe a different approach.)

Ron