Posted by awolfey on August 20, 2008 at 11:56am
I'm having a strange problem with the title on admin pages. When I go to admin/categories, for example, the title is correct: Categories. But when I click the Add Vocabulary tab, the title changes to the "Some User's Blog". This is true for all the admin pages I've tried, and it's always the same user's blog name. Another example: I go to admin/build/block and the title is Blocks. I click the Add Block tab and again the title is "Some User's Blog".
I'm thinking this is a caching problem, but why would it only be the Title that's funny, and why only on tabbed admin pages?
Any ideas?
Thanks
Comments
what theme are you using?
what theme are you using? if anything other than Garland, does this issue occur with Garland also?
Seems to have stopped
It's gone now, all on its own. I bet it was an overworked browser issue solved by a restart. Very strange though.
*'s blog on admin pages
Awolfey, is the problem solved for you? If so, do you remember by any chance what steps you followed to make it displayed correctly? Any thoughts will be appreciated as I continue to have this problem and it's irritating.
I uninstalled some of the modules I installed recently as well as cleared cache and views cache - it didn't do the job.
Am I the only one having this problem??
Very strange
Well, it seemed to be gone since I mentioned it above. Then it was happening again last night, but this morning it's fine. It's still the same user's name showing up.
I wonder if it only happens when he's logged in? next time I see it I'll check.
it's theme independent
It doesn't matter what theme is active. Garland doesn't display the title and it could be deceiving.EDIT:
I posted more info here: http://drupal.org/node/305137
Same here
For a few days now I've been experiencing the same problem. Emptying variable cache and browser cache didn't help, though. I'm using Zen subtheme.
EDIT
I switched to Garland and everything seems to be OK. I've made some changes to my template.php file in my Zen subtheme recently. Could this be it?
ongoing tests
I am still having the problem. I modified the user's name, and the modified name appeared in the second level admin title. I changed it back and the title also switched back to the user's original user name.
So somehow the second level admin titles are actively connected to this single user's username.
Possible solution!
OK, so I gave that user a new uid and retired his old uid. Now the titles appear correctly. We'll see how long it lasts. In the meantime I have to update all the tables with is old uid...posts, comments, etc...
After updating his content with the new uid the problem is back. Now I'm thinking there is some problem with one or more of his posts..his blogs I'm guessing.
When did you start getting this error?
I have been experiencing this problem not for very long. I mean, I began building the website with Drupal 5.7, but I started getting the error maybe 3 weeks ago. I'm trying to recall if I installed any new module at the time, and beside installing Views Popup, Rep[lacement]Tags, Trackback, User Stats and Advanced Forum, I did a few module updates here and there plus I upgraded Drupal core to 5.10. Perhaps we can associate the problem with a particular update?
Recently (during last month, I'd say) I updated (to the current versions) CCK, FeedAPI, Filter Default, Footnotes, Forward, Hierarchical Select, Image Caption, Taxonomy Lineage, Meta tags, Secure Site, Table of Contents, Update Status and Upgrade Status. Once again, after disabling Views Popup everything seems OK.
I'll generate new users and new content and see if this changes anything.
I wish I could remember...
I am also using Image Caption. I'll try disabling that.
Try disabling all
Aaron, you can try disabling all contrib modules and then enable them one by one and see if this will give you an answer to which module is causing the problem. This is how I figured out that it was Views Popup in my case.
Regarding the core modules: I applied two patches as well. Both of them are documented though:
Have you applied any of these as well?
related problem and workaround
http://drupal.org/node/308358