I have updated my module from moodle 3.2 to moodle 3.5 and receive these errors in the debug web console:
moodle-core-event: Global event published: FORM_ERROR
yui_combo.php?rollup/3.17.2/yui-moodlesimple.js:5828 moodle-core-event:
Global event published: BLOCK_CONTENT_UPDATED
These errors show when opening a pop up with atto editor so notes can be saved. Unfortunately, I can't save the notes and it seems the above errors are causing the issue.
I have tracked down a similar error on the moodle forum site:
https://moodle.org/mod/forum/discuss.php?d=367647
However, no solution has been marked. Sadly no apache errors are showing so I can't narrow down the problem.
Can someone shed some light on these errors?
Just checking the obvious, but did you purge the caches? Javascript is cached
Administration > Site administration > Development > Purge all caches
or
php admin/cli/purge_caches.php
I always turn the cache off in config.php in a development environment $CFG->cachejs = false; but never on production, which has caught me out before.
Also, you might need to run grunt to minify the javascript files, then add the minified files to the git repository
https://docs.moodle.org/dev/Grunt
If your javascript is in a folder called amd
grunt amd
If your javascript is in a folder called yui/src/something
grunt shifter
Or just
grunt js
Related
I was fixing things on a not well-maintained typo3 installation and it resulted in blank pages of frontend, backend and install tool.
I wanted to fix extensions because the powermail-extension was not working anymore even after updating to latest compatible version (tried emptying cache and database compare).
I deactivated an extension "compatibility6" to see if it was interfering and since then all pages have been blank including Install Manager. I reactivated the extension via PackageStates.php, emptied the cache but it did not change anything. I was not able to see any error messages even though I set the parameter in LocalConfiguration.php which made it hard to try to find out what is wrong. Then I restored a backup using vmware. Still, backend and frontend are blank.
I am using Apache and Typo3 7.6.23.
I do not know what might be causing the problem and would like to know what else to look for?
It means you have a PHP error there. The first thing would be to examine logs. If you see anything like "class not found", then your next action would be composer dumpautoload --no-dev.
Long time ago I had an article about blank pages in TYPO3 FE. Not up to date but still can be helpful: https://www.dmitry-dulepov.com/2009/03/blank-empty-page-in-typo3.html
Dmitry already wrote it: you have an error.
In production environment nothing is shown for not revealing any information about your system.
So the only information about the error can be found in the error log of your webserver.
What can you do to get more information about your error?
Enter the install tool and switch to develop mode. This will also enable deprecation logging into a file. Try to avoid filling your system with deprecation warnings by disabling deprecation logging.
Disable the default exceptionhandler by adding this to your typoscript setup:
config.contentObjectExceptionHandler = 0
Now you should see a call stack instead of blank screens.
Be aware that this might reveal confidential information from your system.
because of this you should use a copy of the live-system.
I'm working on JSP project in RAD 8.5.5 (when I tried to switch to Eclipse Kepler I've had the same issue) and WebSphere 8.0
When I change something in external JavaScript files which contain my own JavaScript functions I begin to get an error - 'function non defined' or even I lost part of code of this *.js page when I try to debug it in Chrome.
When I publish it to the server or rebuild it doesn't help. When I try to work without javascript cache in Chrome it doesn't work. Only after certain amount of time it begins to work. When I make changes in embedded JavaScript code on JSP page I haven't any problem, only I use my own function in external files.
What can it be? I lost a lot of time on this issue and it's annoying.
Thank you!
To overcome this issue you should do as following:
1.Prevent from browser to cache pages, in Chrome you can do it only developer tools are open : Disabling Chrome cache for website development
2.Perform 'Build project' from Eclipse(RAD). In some difficult case you have to do 'clean' on the server.
3.If you encounter unexpected delay while publishing try to delete all Breakpoints and Expressions from debug perspective.
4.Sometimes your server turning off and on every minutes by itself. To stop such behavior restart it in usual mode and then restart in debug mode.
Hope it will helpful to somebody.
I have installed the Chrome Dev Tools Eclipse plug-in as described on http://code.google.com/p/chromedevtools/ and debugging JavaScript basically works. I can set breakpoints in my JavaScript source files and when I run the JavaScript code in Chrome, Eclipse stops the execution and opens the Debug perspective. Stepping through the code works fine, and I can also see the local and global variables in the Variables view.
When clicking on one of the variables, the detail view shows an error message, though:
Helper script failed on remote: _com_chromium_debug_helper is not defined
Did I miss something during the installation?
Update
Added an issue on the project's page: http://code.google.com/p/chromedevtools/issues/detail?id=85
Most likely you should open an issue at the project page. It is definitely a bug and fixing it might require additional context from you.
This is internals of ChromeDevTools SDK's workaround for WebKit Remote Debugging protocol limitations.
I am trying to debug Magento Code through Eclipse PDT. I configured X-Debugger properly and apply breakpoints in index.php file and launch the debugging session. I started debugging the code line by line but it get stop at last line of index.php file.
Actually i just want to debug the one-page checkout process of Magento. I have applied breakpoints in OnepageController.php file and gone through Onepage Checkout process but Eclipse does not stops at break points. Please help me.
I was busy for many days to find an installation (in 2012) for debugging Magento. Eclipse, Netbeans and PhpDeveloper all failed for XDebug (stopped only at first breakpoint) in a Xamp installation (my experience) and I could not load a ZendDebugger.dll as well. You find indeed a lot of outdated articles about this subject.
But finally I can debug Magento without problems (you need a debugger as a professional for Magento). I downloaded Zend Server CE and if you have a latest Eclipse PDT version downloaded (take the one from Zend) debugging works like a charm (all settings are done already by Zend, so no mistakes and wasting of time anymore). You should see when a webpage had finished that the php program had terminated (no error, is normal, for a next page php programs are started again). One problem yet Connect Manager does not install extensions anymore, BUT while debugging admin it works too (yes funny, but that’s Magento, it takes all your time). You can debug admin by adding /admin to the url in the debug browser window (just that simple).
Now the debugger is working fine, i think the problem was occurring due to wrong configuration of eclipse PDT. To know how to configure eclipse PDT and X-debugger
please visit
http://devzone.zend.com/1147/debugging-php-applications-with-xdebug/
http://subesh.com.np/2010/01/debugging-magento-eclipse-pdt-zend-debugger/
I recently started using git with the egit plugin in eclipse, and I thought I had everything working. I cloned a remote repository to my machine, then made a change to a file, and went to commit the change via selecting the file in the project, and going to Team > Commit.... As soon as I do, I get the following error:
Unhandled event loop exception
org.eclipse.swt.SWTError: No more handles [Unknown Mozilla path (MOZILLA_FIVE_HOME not set)]
at org.eclipse.swt.SWT.error(SWT.java:4308)
at org.eclipse.swt.browser.Mozilla.initMozilla(Mozilla.java:1826)
at org.eclipse.swt.browser.Mozilla.create(Mozilla.java:687)
at org.eclipse.swt.browser.Browser.<init>(Browser.java:96)
...
(output abbreviated)
I am fully willing to accept that this is a bug of sorts (even though I thought this was working earlier today), but I am hoping someone may have encountered this problem once before.
Any insights? Even if it is only who I should file the bug against? I can provide any additional details. I should also point out that things work fine if I commit through the git repository view.
The problem is that the particular git workflow is creating a SWT Browser component that is having trouble loading on your particular OS + Windowing system + mozilla library version combination. There is a bit of black magic that has to go on to make sure you get the right configuration to allow the SWT browser to work with your embedded mozilla renderer. You can get detailed information on the SWT FAQ page here.
Also there are many other posts on this site that talk about how to resolve the dreaded "NO MORE HANDLES" problem here.