Masthead image shows up instead of article image with "Progessive caching"

gbtravel

aman204

I am unable to see any bg-images assigned of currently, to any menu item in JA Masthead module. Ref: Screenshot. Kindly assign some image for it to reflect accordingly. Thereon, The caching issue as mentioned can be examined

Also, When assigning bg-image to Menu item type - Category blog, You may kindly add the suggested css code here in order for added bg-image to reflect

gbtravel

aman204 Yes, I have replaced the bg-masthead.jpg that came with the installation because I could not get masthead module work properly so see this as a workaround.

I have added a picture now for in the masthead module which refers to the category and still it did not show.
I have added a custom.css file in the root of the template folder and still it does not show although you can see the picture coming after CTR+F5 but it is overwritten by the (default) bg-masthead.jpg
I was surpised that I had to add custom.css plus code to get a module working properly?

Can you please have a look what is going on?

gbtravel

Correction. The custom.css should have been in the css folder and now the masthead image - as configured in the module - shows up in the category.
The issue that I am reporting is however not solved. The full picture on the article is still overwritten by the bg-masthead.jpg if the cache is turned on. Turning the cache off makes the picture appear again.

Issue not solved.

aman204

gbtravel The issue that I am reporting is however not solved. The full picture on the article is still overwritten by the bg-masthead.jpg if the cache is turned on. Turning the cache off makes the picture appear again.

Having reviewed with Progressive caching turned on, The bg-image as being set through Masthead module is appearing fine. Kindly view Screenshot for the same

You may also clear your browser cache if changes dont reflect

teitbite

Hi. Is an article titled: "about-gordon-s-bay" a good example of that problem? I've cleared cache and enabled progressive one while still keeping same page opened in other tab. I see no difference between them. Not sure if it's because of clearing cache or is that a bad example of this problem.

gbtravel

aman204 PLEASE!!!! That is not the issue. PLEASE look at the screen shots.
Go to "stay" in the menu and you will see 3 items / https://www.gordonsbay.travel/where-to/stay/
Pick first item look at the picture at the top / https://www.gordonsbay.travel/stay/gordon-s-bay-stay-self-catering-accommodation You will see a terrace plus pool and view on the ocean. Please note that I turned cache off!!!

Ok, now switch cache on and look at the same article / https://www.gordonsbay.travel/stay/gordon-s-bay-stay-self-catering-accommodation / Use SHITF+F5 to refresh.
Picture is now replaced by default masthead picture. This is NOT ok!!!

By the way, this is also not the picture set at the masthead module which shows up in the category view.

aman204

gbtravel Ok, now switch cache on and look at the same article / https://www.gordonsbay.travel/stay/gordon-s-bay-stay-self-catering-accommodation / Use SHITF+F5 to refresh.
Picture is now replaced by default masthead picture. This is NOT ok!!!

Can replicate the relative issue now with several refreshes with Progressive Caching- On. Have reported the bug to JA Dev. Team. Please be patient while we revert back

gbtravel

aman204 Thank you but it is not only with progressive caching, also with conservative.

saguaros

gbtravel

When you enable the cache settings in global configuration, did you publish the System - Page cache plugin also? http://prntscr.com/ksko8e

gbtravel

saguaros Enabled plus ticked browser caching. Looks promising. Will finish testing tomorrow.

paulus1031

Please keep us posted

If you need us to taken another look you will need to check the admin details are correct or enabled

Cheers
Paul

gbtravel

paulus1031 Thanks! Now it works like it should work. I did test them separately but not in a combination and obviously that did the trick. It works fine now so you can close this issue.