[#5739] - Article Manager fails to display after upgrade to Joomla 3.3.6
- Closed
- 16 Jan 2015
- Medium
- Build: master
- # 5739
I have recently upgraded my site to Joomla 3.3.6. All seemed well so I checked in my changes, and began updating my site content.
After about half a day of successfully editing articles and menus, my Article Manager suddenly failed to display anything in both Firefox 34.0.5 and Safari 6.1.6.
Firefox shows http://localhost:8088/administrator/index.php?option=com_content&view=articles as:
Firefox shows http://localhost:8088/administrator/index.php?option=com_content as:
Safari shows a blank white page in both cases. Other Joomla pages - admin and site - are still shown normally, including individual articles (via Control Panel) and the Menu Manager.
A quick search of your error database revealed another user who reported a very similar issue: #4462. However, I can add some further details.
My installation is running on my localhost using MAMP 2.1.3, which has been working flawlessly for over a year without any config changes. Looking at my MAMP logs, I see that the Apache log contains the following error message, which coincides with each failed attempt to view the Article Manager:
[Thu Jan 15 15:03:42 2015] [notice] child pid 11651 exit signal Segmentation fault (11)
MAMP reports Apache/2.2.23 (Unix) mod_ssl/2.2.23 OpenSSL/0.9.8za DAV/2 PHP/5.4.10.
[Update] I have just stopped and restarted my MAMP servers, and the problem has vanished. However, I thought it was still worth reporting as others have experienced similar problems, and this might shed some light on the issue.
| Labels |
Added:
?
|
||
| Labels |
Added:
?
|
||
maybe a issue with your MAMP envoirment. I'm using XAMPP (Windows 8.1)
This comment was created with the J!Tracker Application at issues.joomla.org/joomla-cms/5739.
| Category | ⇒ | Administration Updating |
I use mamp.. Can't confirm
| Status | New | ⇒ | Closed |
| Closed_Date | 0000-00-00 00:00:00 | ⇒ | 2015-01-16 14:36:04 |
| Closed_By | ⇒ | zero-24 |
Thanks @brianteeman
Closing here as we can't reproduce this issue here and is fixed by a server restart thanks for your report @rjksmith
This comment was created with the J!Tracker Application at issues.joomla.org/joomla-cms/5739.
Set to "closed" on behalf of @zero-24 by The JTracker Application at issues.joomla.org/joomla-cms/5739
One day later, the problem has recurred - exactly as I previously described.
[Fri Jan 16 16:38:24 2015] [notice] child pid 13120 exit signal Segmentation fault (11)
I can confirm that I have been developing my website with Joomla for over 2 years now, and this issue has only appeared in the last 2 days, since I updated to Joomla 3.3.6 (from 3.2.1).
- My MAMP installation only supports Joomla, so this is not due to some third party interaction.
- Restarting the MAMP servers corrects the problem, so it is unlikely to be a database corruption.
- It only affects the Article Manager page, which narrows the code search.
- It does not affect the Menu Manager, so it is not in common code to both managers.
- My most-recently edited article can still be displayed in the Article Editor, via Control Panel, so only the manager is affected, not the editor.
I'll leave you to decide how to proceed.
Same problem with a 3.3.6 Joomla website, and it occured from one day to the other on a prod site :(
Unable to access the article view in admin page today, and yesterday everything was fine.
I get an error net::ERR_EMPTY_RESPONSE when trying to access administrator/index.php?option=com_content&view=articles
The categoies view is fine...
Where can I find a solution?
I have just encountered this issue and fixed it by increasing php memory limit in php.ini from 128 to 256MB. But it seems strange that there is segmentation error and not simply message "increase memory limit"
the issue is 99%certainly nothing to do with the memory limit but is
instead the result of a badly coded content plugin
On 22 May 2015 at 13:54, blueboar2 notifications@github.com wrote:
I have just encountered this issue and fixed it by increasing php memory
limit in php.ini from 128 to 256MB. But it seems strange that there is
segmentation error and not simply message "increase memory limit"—
Reply to this email directly or view it on GitHub
#5739 (comment).
Brian Teeman
Co-founder Joomla! and OpenSourceMatters Inc.
http://brian.teeman.net/
A content plugin?
How could it be possible, yesterday, no problem, today that weird error without installation of any new extension in the meantime...
I really don't see where the problem could be within Joomla.
The server side, which I don't manage, seems to be the best suspect, no?
we have the same problem today.
We do the following.
doing an akeeba backup
make a new directory and and new database on the same server
then restore the backup in the new directory and take the new database
for us it works
This comment was created with the J!Tracker Application at issues.joomla.org/joomla-cms/5739.
This is a closed issue. Please don't post here.
I'm going to lock this so it isn't misused any longer.
i can't confirm this. on two upgrades 2.5.28 -> 3.3.6
This comment was created with the J!Tracker Application at issues.joomla.org/joomla-cms/5739.