Thread

Hello all,

I originally posted this as a bug report, but was told to post it here instead.

I’m encountering a lot of apparent bugs, which turn out to be caused by caching. This post details two common examples, both encountered whilst using Safari 5.

Edit Entries Screen
After create a new entry, it doesn’t immediately appear in the Edit Entries screen. Refreshing the page a couple of times displays the new entry just fine.

Changing a Channel’s Short Name
Changing a channel’s short name resulted in my being unable to delete or edit any of the entries associated with that channel.

After encountering this particular problem, I first navigated to the Channel Admin area of the CP to create a test channel, and then published a new entry in this channel (in an attempt to reproduce the problem).

Once that was done, I changed the “test” channel short name, and returned to the “Edit Entries” screen.

The original “problem” entries had now disappeared, having been correctly deleted all along.

However, the new “test” channel was reporting the incorrect channel name, and I once again had issues editing or deleting the test entry.

Refreshing the page a few times solved the issue.

Conclusion
As I mentioned at the start, these are not an isolated incidents; I’m encountering a lot of issues which appear to be due to caching.

I’m still of the opinion that this is not a technical support issue, and should be considered a bug—whether the caching is down to EE or the browser is ultimately irrelevant. Either way, it still results in problems with the usability of the system.

That said, I’m really just interested in finding a solution to this problem, and would be happy to be proven wrong.

Cheers,
Stephen

Hi Stephen,

I’m afraid that I can’t replicate either issue on v2.0.2 20100430 using Safari 5 or Chrome 5.0.375.86 on a local install using MAMP 1.8.2. Is this happening on local or remote installs or both? And on which versions and builds are you seeing this?

Cheers

Greg

Hi Greg,

I’m seeing this on v2.0.2 20100430, both on a local MAMP install (1.8.3), and on a remote Unix server.

It’s happening consistently, and whilst it’s a minor annoyance for me, it’s something I could live with. My concern is that it starts happening for a client, at which point things become a lot more tricky.

I’m not sure where to go from here, as you can’t reproduce the problem. I could record a screencast of it in action, but that’s not going to do anything other than demonstrate what I’ve already described.

Any suggestions?

Stephen

Hi Stephen,

Is there an addon of any type or a particular field type that is common to all the installations where this happens? And does this happen on every channel or only some of them?

Cheers

Greg

Hi Greg,

Is there an addon of any type or a particular field type that is common to all the installations where this happens?

I don’t believe so, but I’ll need to double-check. That may take a few days.

And does this happen on every channel or only some of them?

Again, I believe it’s every channel, but will need to confirm.

Cheers,
Stephen

Sounds good. Let us know what you find out.

We seem to be having the same issue, was there any conclusion on how to correct it?

Triad, is this an EE2.x or an EE1.x issue for you?

Hello all,

A quick update, as I just realised I never followed-up on this thread.

I’ve given up using Safari when working with the EE2 control panel, as there were so many (apparently) caching issues. Newly-created entries wouldn’t appear in the “Edit Entries” list, deleted entries continued to appear in the “Edit Entries” list, and then threw an error when you click on them, loads of stuff like that.

It’s a pain, and something that needs to be addressed, but I’ve managed to work around the issue.

Of considerably more concern is that fact that a client recently experience the same issue with a deleted entry, whilst using Firefox on Windows. After refreshing the page a few times (at my behest), the entries list updated to reflect the latest changes. Clearly this isn’t much of a solution though, and doesn’t inspire client confidence.

This was with EE2.1.1 build 20101020, using the “Corporate” control panel theme.

There’s not much more information I can provide about this, but if you want me to check something specific, just let me know.

Cheers,
Stephen

Hi Stephen,

Which host are you using for this site? Do you have any deflate or expires directives in an .htaccess file?

Cheers

Greg

Hi Greg,

Which host are you using for this site?

This particular site is MediaTemple. I’ve had similar issues when developing locally (using MAMP Pro on Mac OS 10.6.x).

Do you have any deflate or expires directives in an .htaccess file?

Not in the system folder. My folder structure is as follows:

/pub/    # Public root.
/sys/    # System folder.
/tpl/    # Templates.

An .htaccess file containing deflate and expires directives resides in the “pub” folder, but there’s nothing in “sys”.

Cheers,
Stephen

Unfortunately I am unable to reproduce this. We’ll continue looking into this, however. Thanks.

Ingmar / Greg,

A video of some of the weirdness, this time in Google Chrome.

Serious question: what do I need to do to get this acknowledged as a bug?

Stephen

+1 @ Edit screen
I’m having the same issues with that entries, I learned that I need to shift-f5 in FF to get new data, but for client is pain to do that every time. I miss old-fashion postback edit page, there I was at least shure I got the right data.

Also, If I delete some entry from Edit list, I still see that deleted entry there, even with few refreshes. When I try to open it, I got the right message for no existing entry.

An Error Was Encountered
You have tried to access a channel that does not exist.

This was on last Chrome and 2.1.1 Build 20101020

Thanx

I was having a similar problem and it turned out my .htaccess was caching too heavily and cp views were not refreshing when changes were made.

This is my resolved thread about it: http://ellislab.com/forums/viewthread/170410/

Maybe you have looked into it already, but just in case someone is having the same insanely frustrating caching issues I had.