darksoundlab

PRO – Thank you for that.

Thanks for that.

May I ask, since you explained that the debugging option is “simply to display the gallery info of a particular gallery, such as the gallery settings, images added etc.”, is there any issue with just leaving it enabled for the time being, since it at least seems to display the gallery images?

Thanks again Elvis,

I am not able to clone or stage the site on another server due to size and client agreements. If you are able to work with me at a specific time, I can make arrangements to be available at your convenience, and disable the debugging, run tests and make any other changes you require to troubleshoot the issue.

Let me know if this is something you are able to coordinate.

DSL

Thanks Elvis,

I was referring to the debugging in the FooGallery plugin. Once I enabled it and refreshed the page, the images show up. If I disable it and refresh the page, the images are greyed out.

As of now, I have it enabled, which is why you are able to see the images.

I am trying to determine a permanent solution so I don’t have to leave the debugging enabled. Any help you can offer would be greatly appreciated.

Thanks for the reply but, unfortunately I need a solution for visitors that would not require them to disable their browser cache.

I also was not able to find any memory errors through the server.

Any other ideas?

(As an aside, I get proper playback functioning (being able to playback all without having the refresh page) when using the MP3-jPlayer plugin. I just don’t care for the look or the styling, which I am trying to fix.)

Thank you. I will look into it and hopfully get some resolution.

I see. I have tried clearing the browser cache, reloading the page, etc. It apparently seems to only be an issue within Firefox and does however, display correctly in a Private Browser window. Any other ideas?

Thank you for the Timely response. (no pun intended)

Thanks so much for your reply. The path is what is desired so your answer has helped fix the issue. Everything seems to be functioning correctly for now.

Thank you so much for your attention to this matter.

So yes, disabling javascript processing on the Fast Velocity Minify plugin does solve the issue. Thank you for locating the culprit. Is the conflict something that can be bypassed using that plugins feature:

JS and CSS Exceptions

You can use this section to exclude certain CSS or JS files from being processed in case of conflicts while merging.

Where one could point directly to the file(s) that are causing the issue?
I don’t know what file or script is cause the issue though, if you can provide specifics, that might be something I could also try. Thanks.

I will also look into the autoptimize plugin you mentioned.

• This reply was modified 6 years, 4 months ago by darksoundlab.
• This reply was modified 6 years, 4 months ago by darksoundlab.

Yes, they are both checked.

Thank you for the reply.

Will be looking forward to supporting your efforts.