ImpressPages - Unable to add plugin / themes - impresspages

I am new to Impress Pages. Using version 4.2.7 ( Installed 4.2.6 and upgraded from within the CMS). I have the following issues;
Tried to add the "PHP" plugin and got error message
"Plugin signature verification failed" . Plugin is NOT ADDED
I tried to add a new theme and got the error message Unknown error. Please see logs.
Where are these logs ? I have tried /var/log/apache2/error_log , etc.
Update 1: The log within the cms shows ;
2014-11-01 17:00:44 Cron.finished array(0) { } 2014-11-01 17:00:44
Cron.started array(7) { 'firstTimeThisYear' => bool(false)
'firstTimeThisMonth' => bool(false) 'firstTimeThisWeek' => bool(false)
'firstTimeThisDay' => bool(false) 'firstTimeThisHour' => bool(true)
'lastTime' => int(1414828943) 'test' => NULL }
I dont see anything related to plugins or themes ? Is there another log ?

The error says that the signature of the file can't be verified. There may be two reasons for that:
Your server is missing some encryption lib. But I guess current implementation should not require any additional libs.
The downloaded file is not what had to be downloaded. That could be due to DNS errors, network error, etc.
Which case it is can be told only by debugging. You can always download plugins from market.impresspages.org and install them manually.
If you want to debug, first place to look at is file/secure/tmp dir. You should find the downloaded plugin there. Have a look if you can unzip it. If you can un-zip, you have the problem number 1, otherwise 2.
Most likely your server couldn't download files from Internet.
You can

Related

Webpack can not resolve module

I need some guidance. I am experiencing an issue where webpack throws an error that it can not find a module . I was trying to add a require statement of a package(included as dependency). I got it working in another project where I don't need webpack. The code looks basically as follows:
context.subscriptions.push(
vscode.commands.registerCommand("vstodo.helloWorld", () => {
vscode.window.showInformationMessage(
"test"
);
const sfdx = require('sfdx-node');
sfdx.auth.web.login({
setdefaultdevhubusername: true,
setalias: 'HubOrg'
})
.then(() => {
// Display confirmation of source push
console.log('Source pushed to scratch org');
});
}));
My webpack config can be found here
I uploaded a simplified version of the repository here Repository
containing all the configuration files for rollup and webpack.
If I leave out the part starting at the require statement everything works again.
Any help on how to tackle this would be much appreciated, thanks
The vscode extension page has a short troubleshooting guide about this: https://code.visualstudio.com/api/working-with-extensions/bundling-extension#webpack-critical-dependencies.
They suggest the following solutions:
Try to make the dependency static so that it can be bundled.
Exclude that dependency via the externals configuration. Also make sure that those JavaScript files aren't excluded from the packaged extension, using a negated glob pattern in .vscodeignore, for example !node_modules/mySpecialModule.

How unload an extension when i cant login in the backend and the install tool is gone

when upgrading from TYPO3 8.7 to 9.5 i got this error message in the install tool :
Something went wrong. Please use Check for broken extensions to see if a loaded extension breaks this part of the install tool and unload it.
The box below may additionally reveal further details on what went wrong depending on your debug settings. It may help to temporarily switch to debug mode using Settings > Configuration Presets > Debug settings.
If this error happens at an early state and no full exception back trace is shown, it may also help to manually increase debugging output in typo3conf/LocalConfiguration.php:['BE']['debug'] => true, ['SYS']['devIPmask'] => '*', ['SYS']['displayErrors'] => 1,['SYS']['systemLogLevel'] => 0, ['SYS']['exceptionalErrors'] => 12290
Now i am lost because i dont know how to unload an extension ...
- i cant login in the backend
- the install tool is gone - no possibility to get it running again
- typo3conf/autoload is deleted
- typo3temp is deleted
- and in packagestate there is no possibility to unload an extension
I even emptied the complete extension folder but nothing changes.
How is it possible to unload a extension in TYPO3 9 and get the install tool running? Why does it break?
Thanks!
You could either use the command line with
vendor/bin/typo3 extension:deactivate <EXT-KEY>
or delete the array entry for your extension in the file public/typo3conf/PackageStates.php. In both cases, you may need to also clear public/typo3temp/var manually.

Something went wrong with Facebook php sdk in yii

I installed Facebook php sdk as stated in facebook official doc. Moreover, I loaded application configuration into Facebook\Facebook service and replaced required paramters with my own:
$fb = new Facebook\Facebook([
'app_id' => '{app-id}',
'app_secret' => '{app-secret}',
'default_graph_version' => 'v2.8',
]);
However, when I run the project, I got following error:
Fatal error: Class 'Facebook\Facebook' not found in
C:\OpenServer\domains\localhost\blog\protected\controllers\PostController.php
on line 49
I do not know why it is happening. How can i solve it?

Refused to execute script - Strict Mime type [closed]

Closed. This question needs debugging details. It is not currently accepting answers.
Edit the question to include desired behavior, a specific problem or error, and the shortest code necessary to reproduce the problem. This will help others answer the question.
Closed 3 years ago.
Improve this question
Newbie to mediawiki, so apologies if this is a simple error.
I have a local working fine, but on my remote (addon domain, installed in the root of that) my mediawiki install keeps giving me the console error of:
Refused to execute script from
'http://host.co.uk/load.php?debug=false&lang=en&modules=notify%2Cutil%7Cmediawiki.legacy.wikibits&skin=vector&version=5e0d755bcceb'
because its MIME type ('text/html') is not executable, and strict MIME type checking is enabled.
that's in google chrome. But in Firefox i'm getting:
SyntaxError: expected expression, got '<'
This error is on line 1 and points to <!DOCTYPE html>, I'm thinking because it's trying to load html, not JS?
When I initially actioned the install, I wasn't getting any css, I solved this issue setting the session.save_path to a writeable directory.
The page URL on going to the root of the site is different from local to remote. This is because my remote uses CGI which apparently breaks the short urls: see mediaWiki: $wgUsePathInfo
local: /index.php/Main_Page
remote: /index.php?title=Main_Page
I've considered the byte order issues for LocalSettings.php, by saving in vim and checking for a space or dot before <?php, but alas no solution.
My error is described here perfectly, but being on a dedicated VPS and looking at the markup, I'm confident there is no code for tracking or advertising being injected automatically - could there be another cause?
https://www.mediawiki.org/wiki/Manual:Errors_and_symptoms#Missing_edit_toolbar.2C_JavaScript_not_working
The errors do change when I switch from using suPHP as my handler. Changing to FCGI I'm able to get the firefox syntax error expected expression but got < in google chrome and some errors printed to the page of:
Warning: Unknown: open(/tmp/sess_cf912e9c546f88005f99ad715791fe84, O_RDWR) failed: Permission denied (13) in Unknown on line 0
Warning: Unknown: Failed to write session data (files). Please verify that the current setting of session.save_path is correct (/tmp) in Unknown on line 0
I am confused as whilst the least errors come from suPHP, looking in php info it says my php api is CGI/FastCGI
I am using MediaWiki 1.26, php 5.5.3, Apache 2.2.31, CENTOS 6.7 x86_64 - any further details please just ask.
Your help would be greatly appreciated. Apologies if I've missed anything.
UPDATE
The url which is giving the console error:
/load.php?debug=true&lang=en&modules=j…notify%2Cutil%7Cmediawiki.legacy.wikibit‌​s&skin=vector&version=10de47153c1c
returns this javascript object:
mw.loader.state ({
"j…notify": "missing",
"util": "missing",
"mediawiki.legacy.wikibit‌​s": "missing"
})
UPDATE 2
To show any details that perhaps I'm missing I show a screen on the dev tools.
but also, on going to the concerned url again, it's now spitting out further information. I believe the information has changed because in my desperation I did composer install and reploaded the /vendor directory:
mw.loader.implement( "mediawiki.legacy.wikibits", [
"/resources/src/mediawiki.legacy/wikibits.js"
] );
mw.loader.state( {
"j…notify": "missing",
"util": "missing"
} );
UPDATE 3
UPDATE 4
Following along the advice from #TGR, I looked at the url in the network tab giving content type text/html. The part that confused me is that it doesn't match the url giving the error. However it does return 302. Looking at the same url on my local install returns:
mw.loader.implement( "jquery.accessKeyLabel", [
"/resources/src/jquery/jquery.accessKeyLabel.js"
], {}, {"brackets":"[$1]","word-separator":" "}
);
mw.loader.implement(
"jquery.client", [
"/resources/lib/jquery.client/jquery.client.js"
] );
mw.loader.implement( "mediawiki.RegExp", [
"/resources/src/mediawiki/mediawiki.RegExp.js"
] );
mw.loader.implement( "mediawiki.notify", [
"/resources/src/mediawiki/mediawiki.notify.js"
] );
mw.loader.implement( "mediawiki.util", [
"/resources/src/mediawiki/mediawiki.util.js"
] );
mw.loader.implement( "mediawiki.legacy.wikibits", [
"/resources/src/mediawiki.legacy/wikibits.js"
] );
I can also confirm that those files in the above code block are present on the problematic wiki.
UPDATE 5
I have just done a new install of the media wiki at a different subdomain. This time rather than FTP I have SSH into the server a ran wget https://releases.wikimedia.org/mediawiki/1.26/mediawiki-1.26.2.tar.gz and then tar xvzf mediawiki-1.26.2.tar.gz. This leaves me with folder 'mediawiki-1.26.2'. I then cd mediawiki-1.26.2 followed by mv * ../ so that the wiki will work from the root. The last thing to do before I can run the install, is to correct the permissions. chown -R user:group *
I then run the install which goes very smoothly. When I get to the homepage and inspect the developer console I get the same error. This is completely fresh, no .htaccess or .conf
UPDATE 6
I felt as though there was some longevity in exploring the install directory. So on my own VPS I followed the install above, again moving files to the Root. I didn't get the same error, but I did get
SyntaxError: expected expression, got '<'
I then installed again but I left it in the subfolder of the root. This has not given me any errors. I then tried this on the live remote that i've been having issues with. Even installed in the subfolder this gives me:
SyntaxError: expected expression, got '<'
If I introduce a .htaccess file to rewrite the base url, such as RewriteRule ^/*$ %{DOCUMENT_ROOT}/mw/index.php [L], then the issue with MIME type text/html returns. Yet adding the same rule on my other install is error free.

chrome.storage is undefined in chrome extension

I'm developing a Google Chrome extension, and have been working on one for a while. So it's been installed for a while, and I updated the manifest file to include the "storage" permission and reloaded the extension. However, when I try it in the console, chrome.storage is undefined. I restarted Chrome and still nothing.
My manifest file looks like this:
{
... snip ...
"permissions": [
"tabs",
"http://*/*",
"https://*/*",
"chrome://favicon/",
"storage"
]
}
I could reinstall the application, but I'm hesitant, since: Will it be the same for the existing users of the extension? It says in the documentation that the permission won't show any warnings or temporarily block the extension for adding more permissions.
My question is mainly, how will the existing users of my extension be affected? Will they get a warning and have the extension disabled until they actively enable it? Or is it just a local develpment issue?
Your manifest looks fine. Did you reload your extension after making the change?
I pasted your manifest permissions into a new extension and called:
console.log(chrome.storage);
And recieved the following:
Note "local" and "sync", the two types of storage available to the extension.