When in Yii 1.1.14 I get some critical error or even not critical warning I get standart error message and all page output is hidden.
I would like in debugging mode :
1) to see all page output when was outputing before error.
Thanks!
You can just enable yii debuging mode in main index.php. Set true if there is false.
defined('YII_DEBUG') or define('YII_DEBUG', true);
Related
I'm trying to get Modules working on a MediaWiki site.
When I try {{#invoke:Test|hello}} I get an error, 'Script error: No such module "Test".'. The Test module has been created, it is the example "Hello World" script from the https://www.mediawiki.org/wiki/Lua/Scripting page.
I have tried with $wgCapitalLinks set to both true/false and also without the variable included at all.
Any ideas of what the problem is would be much appreciated.
I'm trying to override the csp module of magento but I get an error i don't understand : Unknown module
here is my module.xml registration.php the error i get
First try Running, your module will be enabled auto if everything good.
php bin/magento s:up
Also Check your directory is correct, i see in screenshots app/Code , c needs to be small.
Hope it helps!!
I'm trying to upload a file using jQuery 3.3.1 in Safari 12.1.2 and it allows me to browse and select the file that needs to be uploaded. But when I try to upload the selected file. It does nothing. No error message is displayed, at least in the browser console. This is working fine in Safari versions below 12.1.2, Chrome and Firefox. Can some one please let me know a clue to at least start troubleshooting this issue. (I also tried to debug the code but it ended up in jQuery-3.3.1.min.js and terminates.)
Found the change required to fix the issue. Option "forceIframeTransport" In the code snippet that refers to the fileupload function in jdeQuery-File-Upload has been set to "true" in my code. (As per the jQuery-File-Upload doc this value is set to false by default) How ever for a unknown reason file upload fails in Safari 12.1.2 and above when this value is set to true. So simple the fix in my case is setting "forceIframeTransport" to "false" as shown in below code snippet. (please note that it's not required to have cross cite file uploads which is affected by this option in my application)
$('.assetupload').fileupload({
**forceIframeTransport : false**,
add : function(e, data) {
.......
.......
});
i've loaded a backup from an old prestashop 1.4.6.2 website on a subdomain. now i'm experiencing some problems with the module page. whenever i want to expand a module category it refers me to a 404 page. i have error reporting on and only have one error :
Strict Standards: Declaration of jbx_custominvoice::l() should be compatible with ModuleCore::l($string, $specific = false, $id_lang = NULL) in public_html/presta1.4/classes/Module.php(551) : eval()'d code on line 149
I checked if it was just as easy as adding those variables to the function, but that didnt change anything except make the error go away. Also when i look in the console from chrome i see the error:
Uncaught TypeError: $(...).on is not a function
I've looked all over google and prestashop forums but couldnt find a working solution.
I think it can be a firewall to block the access issue
When I run a test that throws a PHP fatal error, I see my default layout (View/Layouts/default.ctp) in the output, inside CakePHP's core layout for test.php. This only happens when a fatal error occurs. Worse, content about the error is injected into the middle of some of my styled artifacts inside default.ctp, making it hard to read.
If I run a test, especially a test that does not invoke a controller, why should render() ever be called on my default layout for content?
The question is tagged 'cakephp-2.1' but could you be using a Cake core of version 2.2? This version has introduced the new error layout.
You should copy this file from: lib/Cake/View/Layouts/error.ctp to: app/View/Layouts/.
Check the migration guide.