Closed
Bug 804058
Opened 12 years ago
Closed 12 years ago
Wiki on getfirebug.com has a memcache error
Categories
(Infrastructure & Operations Graveyard :: WebOps: Other, task)
Infrastructure & Operations Graveyard
WebOps: Other
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: sebo, Assigned: jd)
References
()
Details
(Whiteboard: [firebug-p1])
Attachments
(1 file)
297.43 KB,
image/jpeg
|
Details |
When I visit the Firebug Menu[1] description inside the wiki[1] I see the following error at the top of the page: Strict Standards: Only variables should be passed by reference in /data/www/getfirebug.com/getfirebug/wiki/includes/memcached-client.php on line 1031 See the attached screenshot. Sebastian [1] https://getfirebug.com/wiki/index.php/Firebug_Menu
Reporter | ||
Comment 1•12 years ago
|
||
Updated•12 years ago
|
Assignee: nobody → server-ops-webops
Group: websites-security
Severity: critical → major
Status: UNCONFIRMED → NEW
Component: getfirebug.com → Server Operations: Web Operations
Ever confirmed: true
Priority: P1 → --
Product: Websites → mozilla.org
QA Contact: cshields
Version: unspecified → other
Comment 2•12 years ago
|
||
Could we get some help with this please? The wiki is the most important source of info for Firebug users. Honza
Whiteboard: [firebug-p1]
Assignee | ||
Comment 3•12 years ago
|
||
Honza, These pages were stuck in the application cache and were left over from my testing on Friday. I am a bit surprised that they are still around, you might want to look into how ling it takes your wiki to expire old cache items, just a suggestion. Let me know if you run into any more of these. Regards
Assignee: server-ops-webops → jcrowe
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
Comment 4•12 years ago
|
||
Thanks for quick fix Jason! Honza
Updated•11 years ago
|
Component: Server Operations: Web Operations → WebOps: Other
Product: mozilla.org → Infrastructure & Operations
Updated•5 years ago
|
Product: Infrastructure & Operations → Infrastructure & Operations Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•