After updating the Creative theme to version 1.3 and deleting a few unused modules, I noticed a message when I log out:
Notice: ob_get_clean(): failed to discard buffer of _shutdown_function (2) in theme_render_template() (line 1520 of ... theme.inc).
The website layout changed and the content of some blocks is displayed on the top page (wrong place) as shown below.
There is not much info on this problem on the web and I've reported this as a Drupal bug, but I thought I'd ask here too. If anyone has ideas how to deal with this issue, please post your suggestions.
Related
Running WSo2 EMM 1.1.0, everything has been working just fine except for one big issue.
From the moment I first click on an app in the App Management tab, the WSO2EMM_DB.h2.db file starts to steadily grow as long as the server is running, even with absolutely no changes. Eventually, it gets so big that clicking an app on that tab takes a ridiculously long time to load the list of devices using the app. We're talking 5+ minutes, it becomes completely unusable. I have checked the error logs and found no errors at all, every time.
Restarting the server does nothing to correct the issue. Even if I click an app on the App Management tab once, and never again, the database file will continue to grow. Even restarting the server and not logging into the EMM page, it will continue to grow.
The only thing I've found so far that can possibly help is keeping backup copies of the database file and overwriting the current file when it gets too big. Obviously that's not a solution, as I'd need to create a new backup file every time there's a change on the server, and eventually the database file would grow too big from that too.
It's not an issue with the H2 database either. Not only have I tried starting over fresh several times and have had the same behavior, but here is the only info I could find regarding this issue, and they were having the issue regardless of whether or not it was on H2 or MySQL.
I've been trying to find a solution for this for over a month with no success. Any help would be appreciated!
EDIT: It looks like this might be the subject of EMM-826. Unfortunately there seems to be no response to that bug report so far.
EDIT 2: EMM-826 was closed with a message saying the following:
This issue is fixed in the EMM 1.1.0 GA latest pack. Please get all the patches for the product/build the product from the latest source [ https://github.com/wso2/product-emm ] and try again.
Unfortunately, that did not work for me. I'm not sure what exactly I'm doing wrong, so I'll list the what I did to try to fix it:
Downloaded the EMM 1.1.0 zip from http://wso2.com/products/enterprise-mobility-manager/.
Downloaded the zip from https://github.com/wso2/product-emm and pasted the files from that into my EMM_HOME directory.
When that didn't work, I searched for patches and found I was only using patches 1-6. In the documentation I found I could download patches 7-12 here. Patches 9 and 10 didn't work right for some reason; causing me not to be able to reach the EMM dashboard or publisher. I could only access the Carbon manager. I was able to make patches 7, 8, 11, and 12 work though - with no change in behavior.
Here are the steps I take to reproduce the issue:
After setting a fresh copy of the EMM up, I log in to the EMM dashboard as Admin, set up a user account, and upload an app through the Publisher.
Register a device to the user account I set up. In this case, an Android device running Android 4.2.2.
From the dashboard, I go to App Management and click the app I uploaded. The list of devices loads, but from that point on, the database file starts growing and eventually, after several hours, becomes so large it the device list will never load.
Please help!
Found this happening also, from a quick look it's the WSO2EMM_DB.notifications table. Seems to keep a history of all notifications over time, and the info for app installs is taken from non-optimized queries, which degrade as the table grows. You 'could' delete all rows from the table, and it will re-populate as devices 'check back' and report their info.
But you'd probably want to write a query to just keep the latest notification of each type of each user (I'll leave that to someone else...) and as was mentioned, it is apparently fixed in the latest version.
Issue appears to be resolved in EMM 2.0, which can be found here.
Thanks in advanced for looking at my post! I developed this Commerce Kickstart site locally using Aquia Dev Desktop and everything looked and functioned great. When I post it to the server, I get the WSOD, and an error in the error_log:
PHP Fatal error: Call to undefined function delta_get_current() in /xxx/xxx/xxx/profiles/commerce_kickstart/themes/omega/alpha/includes/alpha.inc on line 222
This is a site that had been working fine remotely also, except for an issue with the checkout. (the original reason for taking it down.) I had to refer to a backup copy of the site, make some changes to get it to be more recent and then post it. That's when I received the WSOD and Php Fatal Errors.
If you have any advice on how to fix or where to proceed, please let me know. Also, let me know if you need any more info.
Thanks again.
Jason
You need to make sure that you're working with the right module and theme versions. See what you can do to update Delta to fix it, also update Omega.
The current project i am working on consists of 2 parts. 1 part is a
qooxdoo app. And the other is a html file that will be rendered in the
browser widget of qooxdoo.
I recently had to make some changes to the second part (not touching
qooxdoo).
After i copied over the files i needed to connect the Qx app to the html
page. Then it gave me some errors.
I taught if i rebuild, they might go away (they did not).
I get the following error:
LOG: 003045 qx.core.Init: Load runtime: 3044ms
SCRIPT5: The system cannot locate the resource specified.
Xhr.js, line 375 character 9
I have looked and the file is located where it should be.
Does anyone has any idea how to fix this or what is causing it?
It was rather silly, i placed one too many parenthesis and that caused the error. I had trouble finding it since the 2 where very unrelated.
I'm in the process of standing up a new CakePHP project with some very simple boilerplate code. In the process of helping a co-working install the code, I realized that if my debug value is 0, I get a 404 error (just loading the homepage):
Error: The requested address '/' was not found on this server.
If I flip the debug value to 1 or 2, the error goes away and the default homepage (I don't have any custom layout/page created yet) loads happily. This isn't an ajax request and there's nothing fancy going on here. Anyone seen this before? Haven't found anything via Google that matches what I'm seeing.
Thanks.
UPDATE
And, just in case anyone is thinking the obvious, my homepage (/) route is configured. Like most everything else, my routes.php file hasn't been modified yet.
Oh, my. Talk about a punitive headslap moment: https://stackoverflow.com/a/3803076/1665
What a long week. I'll mark this answered as soon as the time limit expires. Sheesh...
Try deleting tmp files located at /app/tmp/cache/.
I found solution to similar problem here:
http://cakephp.1045679.n5.nabble.com/Re-Not-found-error-with-DEBUG-0-td1257613.html
We use custom settings in a SalesForce app. We access it like so:
MySettings__c settings = MySettings__c.getOrgDefaults();
This was working fine, but today the app completely crashed. By that I mean the page doesn't load at all, I just get a white screen telling me an internal error occurred. We traced it down to this line of code - when it is commented out the page loads as well as it can without those settings (but at least it loads).
Running that single line of code in the System Log (using the Execute functionality) also causes a report of Internal System Error. The only thing the system log reports is "FATAL_ERROR Internal Salesforce.com Error." The Apex code modal reports "Internal System Error: 1018505045-332 (-920440070)"
The setting has values for the organization - we've also tried deleting the settings and recreating them to no affect. So far SalesForce has been no help beyond telling us to ask on their website.
This is very frustrating as it was working fine on Friday and today it was broken before anyone touched anything.
What you have there is a platform error. Whenever you get those you should report them to SFDC support and they will be able to see further internal logging to sort it out.
Nothing anyone out here can do to help I am afraid.
Paul
try setting the apiVersion of the affected code back to version 21.0. We had the same issue and making this change has provided an effective workaround.
This was a bug in Salesforce's infrastructure, which has been reported resolved. If you're still seeing this error with API version 22.0, you should create a case with salesforce support.