It happens everywhere since the error comes when it is trying to load one of the screens xml files. I see it a lot on file assets, but that is probably because I edit them often. But I have seen it on Page Assets too.
Do you have any non-standard php settings?
Memory limits, suhosin changes etc?
Do you have any non-standard php settings?
Memory limits, suhosin changes etc?
I don't think so, no. I have made changes to Suhosin as recommended, max post name, etc.
I was told that another Squiz client had this issue too, so I wonder what might be the same on our systems.
BTW, today we upgraded to 4.14.1 and are hoping that somehow it will have fixed the issue.
I don't think so, no. I have made changes to Suhosin as recommended, max post name, etc.
I was told that another Squiz client had this issue too, so I wonder what might be the same on our systems.
BTW, today we upgraded to 4.14.1 and are hoping that somehow it will have fixed the issue.
I'm starting to clutch at straws so I hope so. Is it assets with a particular design, or particular metadata schema (or workflow), or status? In a particular area of your system? I'm just trying to narrow down some ideas because the base system I set up is working normally.
I'm starting to clutch at straws so I hope so. Is it assets with a particular design, or particular metadata schema (or workflow), or status? In a particular area of your system? I'm just trying to narrow down some ideas because the base system I set up is working normally.
Well, I do know that the problem appear, and we decided to move our entire site to a brand new VM. We built that with Wheezy and brought over our site and the problem showed up again, so that was pretty frustrating.
Doesn't happen on assets with a specific design because it happens all the time to File assets that don't have designs or paint layouts. These files are in the Media folder.
We were running on 4.10.0 and that is where we have seen all the errors. Used 4.14.1 for only 20 minutes and have yet to see the error.
Hi Nic,
Has 4.14.1 shown the problem again? I'll have to go through the change logs to check for anything that might have helped this, I don't remember anything off the top of my head.
Has 4.14.1 shown the problem again? I'll have to go through the change logs to check for anything that might have helped this, I don't remember anything off the top of my head.
No, we actually have not seen it again. I still want to give it another week or two to say for sure, but it seems like the upgrade fixed the issue.
Just in case anyone else has this error, this is the cause of the issue:
diff --git core/lib/asset_map/asset_map.inc b/core/lib/asset_map/asset_map.inc
index 247ca24..2dfd4ec 100644
--- core/lib/asset_map/asset_map.inc
+++ core/lib/asset_map/asset_map.inc
@@ -590,6 +590,8 @@ class Asset_Map
if (function_exists('libxml_disable_entity_loader'))
libxml_disable_entity_loader(TRUE);
$root = simplexml_load_string($xml);
+ if (function_exists('libxml_disable_entity_loader'))
+ libxml_disable_entity_loader(FALSE);
switch ($root['action']) {
case 'get translations'
I've suddenly come to the same problem and was starting to fill with the frusration of failing to do the bits that I wanted to do. It seems as though the issue is spreading as more assets become unusable. Glad that UoEbusiness has found the problem. What is the solution?