Invoking mediawiki module fails with the error 'Script error: No such module "Test".' - module

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.

Related

Cannot use import statement outside a module when using wrangler v2

I'm new to using cloudflare and wrangler. I've a project that I've been working on, and I'm now trying to deploy it using wrangler publish, but I keep running into issues. My product is coded in node.js, and I'm using version 2 of wrangler. When I execute wrangler publish I get:
Basic JavaScript project found. Skipping unnecessary build!
Error: Something went wrong with the request to Cloudflare...
Uncaught SyntaxError: Cannot use import statement outside a module
at worker.js:2Basic JavaScript project found. Skipping unnecessary build!
Error: Something went wrong with the request to Cloudflare...
Uncaught SyntaxError: Cannot use import statement outside a module
at worker.js:2
I've searched for a solution, and one of them that I found said to change module in wrangler.toml from type="javascript"to type="webpack" however that gives me a bunch of errors:
./node_modules/destroy/index.js
Module not found: Error: Can't resolve 'fs' ... Parsed request is a module...resolve as module
/Users/Desktop/APIs/cpiCalculator2/node_modules/destroy/node_modules doesn't exist or is not a directory
...
Error: webpack returned an error. You may be able to resolve this issue by running npm install.
I've tried reinstalling npm as it suggests and then wrangler publish again, but that just gives me the same error message.
I'm really not sure what the issue is, and I would really appreciate any help or advice on how to resolve this issue. Thank you!
Also, just a note, I'm not sure if this is affecting it, but I do have two other js documents in the main area of my project (where my index.js file is).

Prestashop module page not working

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

ejabberd hook execution error while trying building a message receipts module

I am getting an error while trying to return a receipt message from server to acknowledge message received at server for which I am using a non official module (mod_stanza_ack) and ejabberd 15.07.
I have compiled and configured it successfully too, but it's giving the following error during ejabberd hook execution:
#ejabberd_hooks:run_fold1:371 {undef,[{mod_send_receipt,on_user_send_packet,[{xmlel,<<"message">>,[{<<"id">>,<<"6uAAO-218">>}.....
undef means the function mod_send_receipt:on_user_send_packet.
I see possible reason for this:
source file is not compiled (due to syntax error for example)
or the resulting .beam file is not in your Erlang VM code path
or the function is actually not defined in your module
You need to fix your module accordingly or put the .beam file in the right place.

PrestaShop Fatal error in module Api: syntax error, unexpected T_FUNCTION, expecting ')'

When I enter prestashop back office and click the modules tab in the top menu it is giving the following error, prestashop version 1.5.3.1
[PrestaShop] Fatal error in module Api:
syntax error, unexpected T_FUNCTION, expecting ')'
Any help would be greatly appreciated, searched prestashop forums and cannot find a solution
Thanks in advance
It may be related to version of PHP. I had this problem because of unsupported version of module. What I did was turn on the debug mode on PrestaShop which showed me in what module error was happening and then just removed that module from PrestaShop installation diretory, modules folder.
If you are using that module, you could backup it, then re-installing it, etc.
It turned out it was a problem with Youstice v1.7.2 module
It was causing the API error, what we did in the end was change the name of a folder in the public_html>modules from- "yousticeresolutionsystem" to "yousticeresolutionsystemX"
because it wouldn't allow me to delete the folder to stop the API error.
By using X this in effect deletes the folder stopping the error

Adobe Air Application-sandbox content cannot access this feature

Error #3207: Application-sandbox content cannot access this feature.: SecurityError: Error #3207: Application-sandbox content cannot access this feature.
at flash.system::Security$/allowDomain()
Hi all,
I have an air project that I am trying to run via a terminal using run-air command. If I run it in flash builder it seems to run with no errors, but after using a makefile to build the project and then run the code via run-air in the terminal I get the above error. Before I Was getting the same error and put a try catch around the code, however, I can't do that in this part of the code and don't want to put a try catch everywhere I get this error. I would rather just fix it. It seems to get called whenever my code is trying to access a class via a swc or import.
Anyone have suggestions?
I have tried:
Security.allowDomain("*");
which through the same error, so I put a try catch around it and now it moves on and I Get the above error when I Try to load a swc.
Also we are adding the src folder to the class that is throwing the error above via the compiler properties (we are doing unit tests) and using a makefile to build the project. If we didn't put it in compiler properties the class never seems to get picked up.