Hello,

What exactly happens when you try to fill those composer fields and save? Do they show up empty after saving? Is the page actually modified?

Did you create that page after setting up composer on that page type or did you first set up your composer and then created the page?

Hi Nour

Hope all is good with you.

It almost looks like a caching issue
I have added another video athttp://cl.ly/0t0u3X293c21

I did create the page after setting up composer.
As you can see from the video, selecting the categories end up "empty" after saving and then returning to composer.

Nour

I just noticed that there are newer versions of the s/w, even though "check for updates" does not indicate there are newer versions.

May well be worth updating to 8.3.2?

Hey Kevin. I didn't know if you'd remember me :-)

I'll check your video in a little bit. Concerning 8.3.2 it has its own set of bugs and I don't know if this particular issue was listed anywhere to be fixed.

You should check the changelogs for all the versions since 8.2.1 and see if anything composer related pops up

Here are the links:
https://documentation.concrete5.org/developers/background/version-hi...
https://documentation.concrete5.org/developers/background/version-hi...
https://documentation.concrete5.org/developers/background/version-hi...

Nour

Yes, of course, I remember you :-)

Nothing really about composer. But mentions of caching issues, albeit not directly related to the issue we are having.

The mystery seems to get deeper. We have the same site on a development server and it seems to be working correctly. There must be a setting on the server...but thats way out of my understanding.

I have attached the environment from the working server.

Hi Kevin,
I had a look at your second video and I have some theories that you could test.

First, when you select two categories from the topic attribute and publish, those 2 categories show up correctly on the page. From your experiment, I think we can say it saves correctly Same goes for the other fields.

The problem starts when editing the composer fields again and it seems it doesn't display the saved values correctly. So of course if you save again while those categories are not checked then they won't appear on the page. This, again, is consistent with a saving process working normally.

But then when editing your composer fields, values are visible, at least the ones saved before. And after emptying the cache, it seems the values appear.

So I agree with you there seems to be some cache issue but that's not Concrete5's cache, that's the browser's cache.

That's where my 2 theories come into play.

First I noticed you are using Chrome. I recently had some issues with Chrome caching that was overly aggressive for no reason. One thing you should try is, after publishing, and before editing your composer fields again, open Chrome's developer's tools. Then with the tools open, refresh the page by hitting ctrl+F5 on your keyboard. Or you can also do a long click on the browser's refresh button and a drop-down will appear. Click on the last choice "empty cache and hard reload". Then try to edit your composer fields and see if they are showing the proper values.

If you can confirm that indeed it seems that's working you should check 2 things:
1- check in a different browser to see if you have the same issue
2- if you do, check caching directives in your .htaccess file.

Hi,

Thanks the reply.

I was unable to save topics in composer.

I removed these lines from .htaccess file.
.

Then it worked.as expected. This was added after pen test from another client. Please could you help with what we should put in here.

Thank you Stephanie