Using Notes 8.5.3, UP1, I have a long XPage which uses a lot of ExtLib functions. I'm also using TinyMCE and a jQuery table of contents, described here: http://xomino.com/2012/08/26/jquery-in-xpages-14-toc-create-a-menu-to-scroll-to-a-form-section/. When I create a new document it works fine and saves properly. However, once it's opened in edit mode again, I get the following errors in Firebug:
TypeError: node is null
dojo.js, line 14.
Error parsing in _ContentSetter#Setter_view:id1:id9:callback:tabName_pane_6
file "xsp/.ibmxspres/.mini/dojo/.en-us/#Fv&#EOb&#EOd&#EOf&#Ek&#Es&#Ie&#Ig.js", line 82
Error undefined running custom onLoad code: This deferred has already been resolved.
file "xsp/.ibmxspres/.mini/dojo/.en-us/#Fv&#EOb&#EOd&#EOf&#Ek&#Es&#Ie&#Ig.js", line 82
Basically, these errors are preventing any SSJS from being triggered at all. Any suggestions on how to debug this?
Related
I am new to Vue.js and originally to testing.
so I am trying to write test for my component but this error occurs and I don't know were this error raises from and how to resolve it.
console error image
and this is the test code that I'm trying to execute.
test file
I'm following the Sanity docs on how to add a content preview. After updating the sanity.json and adding a resolveProductionUrl.js file according to docs I should be able to see a menu item in context menu:
But it's not happening. Interestingly enough If I add a console log to a resolveProductionUrl.js I can see it on the browser console - meaning that this function is getting called.
This is what I see:
I ran into a similar issue while following along using Sanity's Preview content on site article.
There were three things I had to do after following their article in order to get it to work:
I had do add this line in sanity.json under plugins
add highlighting to the line:
"plugins": [
...
"#sanity/production-preview"
],
(I didn't add this line to my sanity.json file on the first attempt. The article did not highlight that line, so looks like its just provided as context since the parts entry is highlighted.)
I also had to update resolveProductionUrl.js to use document._id instead of document.slug.current as slug is undefined for me and it was throwing errors in the console (and not showing the menu item).
I had to completely stop the site and re-run sanity start to get it to be picked up locally.
My error_log file keeps getting filled with this error and i don't know what is causing it. Any idea how i can find what is causing the error ?
[14-Aug-2020 13:20:32 Europe/Bucharest] PHP Fatal error: Uncaught --> Smarty: 0():Missing '$template' parameter <--
thrown in /home/website/public_html/vendor/smarty/smarty/libs/sysplugins/smarty_internal_templatebase.php on line 177
It means somewhere in the code there is a variable called {$template} which is not defined. It could be theme templates or modules
I would use IDE to look for this variable. If this doesnt work just go for debuging technique, start where smarty starts rendering and go till place where it crashes :)
It looks like it is a dublicate for this question, maybe will help
SmartyException 0():Missing '$template' parameter with Prestashop
This also might be due to messed up module structure, its ModuleFrontControllers etc.
You can try to edit this file:
thrown in /home/website/public_html/vendor/smarty/smarty/libs/sysplugins/smarty_internal_templatebase.php on line 177
and check if you can log more informations about an error, file path etc.
In a handler in one of my controllers, I'm running into issues displaying a simple alert message. Using Sencha Touch 2.4.1
Ext.Msg.alert('Status', 'test');
--> "Uncaught TypeError: Cannot read property 'alert' of undefined"
As per these instructions, I added the following require statement: Ext.window.MessageBox to my controller.
--> Failed to find any files for /PATH/FILE.js::ClassRequire::Ext.window.MessageBox
Replaced Msg with MessageBox and removed require statement.
Ext.MessageBox.alert('Status', 'test')
--> "Uncaught TypeError: undefined is not a function"
Ran into the same problem when using .confirm.
Here's the docs - looks like it should work.
Anybody know why it doesn't?
I needed to require Ext.MessageBox instead of Ext.window.MessageBox and had to use Ext.Msg.alert... instead of Ext.MessageBox.alert... though I'm not totally clear on why.
Saw this in the docs: "The framework provides a global singleton Ext.Msg for common usage which you should use in most cases."
Good day,
Does anyone know the solution to the following problem?
I have recently set up the Advanced Custom Fields plugin with a custom post template and have been using Gravity Forms to submit post data. Everything seemed to be working fine on a number of posts. However, I went to update a post through the post editor screen and when I clicked on 'update' or 'preview' I got the following error:
Warning: array_merge() [function.array-merge]: Argument #2 is not an array in /home/uswfeoab/public_html/wp-content/plugins/advanced-custom-fields/core/fields/_functions.php on line 396
This was repeated 8 times before the following error code:
Warning: Cannot modify header information - headers already sent by (output started at /home/uswfeoab/public_html/wp-content/plugins/advanced-custom-fields/core/fields/_functions.php:396) in /home/uswfeoab/public_html/wp-includes/pluggable.php on line 876
I have had a good look at the forums and the ACF website but can't find any troubleshooting for errors relating to the _functions.php file. For reference the line of code on line 396 is $field = array_merge($defaults, $field);
Unfortunately this is way beyond my PHP skills. Any suggestions would be greatly appreciated!
Phew!
The author of Advanced Custom Fields issued and update to Version 4.1.2 today. This has resolved the problem.
Panic over!