impresspages 4.0.13 linking to outside websites - impresspages

On my website when using impresspages 4.0.13 when I click add link and type in, http://google.com, for example it turns it into http://glymm-mere.org/12thnight/\"http:/google.com\". Needless to say does not work, how do I fix this? I have tried reentering after the fact but it will only re correct to the bogus website link.

I had this problem also
just add this into .htacces file:
php_flag magic_quotes_gpc off
problem solved

Or just update ImpressPages. Just made ImpressPages to work even if magic quotes are on.

Please turn off magic quotes on your server.

Related

Bigcommerce - Is there a way to add <script> code to every page programatically?

I am developing new app for Bigcommerce and I need to add script tag to every page in the shop.
Is there any way to do that progragrammatically?
It's not a nice way but you can append and prepend php files via .htaccess after that you could modify the output via php script.
Depending on the framework an how you get access to the output.
php_value auto_prepend_file "/dir/path/test.php"
php_value auto_append_file "/dir/path/test.php"
If you already have a template file for the or anything that each file uses, then you can add it there. Otherwise you might be able to write a script to do that for you, but it's probably not worth your time.
Yes you can add code in footer.html and it will reflect on every page.
You can find this footer.html file in template/panels/
Footer.html call in whole BC site so you can add your code here.
I hope this will help you.

How to solve prestashop infinite redirection loop under ssl?

Don't know, maybe someone had the same problem before..
I've got a correctly configured ssl certificate in my server.
If I activate prestashop ssl mode, then several pages generate an infinite redirection loop warning....
I really can't figure out why..
One thing I can say, is that in backoffice, clicking on the ssl acivation link, it does not activate it: it stays, silently, no rerrors, nothing.
So to activate ssl I had to manually change the relevant config variable on the DB.
This could maybe be a symptom of something wrong on the server?
Anyone had the same problem?
Thank you
Apart from upgrading to v1.6.0.11, the solution was to add SetEnv HTTPS On at the very top of .htaccess. That's because several prestashop functions rely on $_SERVER['HTTPS'] and/or $_SERVER['SSL'] vars to guess the urls. One of the most notable functions using them and itself used by many others is Tools::usingSecureMode(). Simply those vars weren't visible before adding SetEnv HTTPS On.
Anyway, this is not to be considered a universal solution, because for example in my local MAMP installation I didn't have the same issue: just worked. I only needed the tweak for the remote server.
Beside this, also note that in backoffice, unde url/seo prefs, I disabled the apache multiviews.
Hope it helps

Edit/Change 300 Multiple Choices on Server

I edited all my server http status messages...
The 300 Multiple Choice is still showing up, when I'm typing in a wrong address, so it's showing me options.
Do you know how I can get rid of that? I don't want users to have a choice. Either I want to redirect to .index.html or I want to show an own created message page with a '>Go back!' option.
Server is apache...
I would appreciate some help :) (If there's a solution for my problem)
thx ahead!
Add this to your .htaccess file:
Options -MultiViews
CheckSpelling off
I solved it a different way without using RewriteRules to fix this..
If you have index.html or index.htm as the first values in DirectoryIndex it will try to load those up first.. I put index.php as the first script to load up and the Multiple Choices 300 error went away. Although I never even had the Multiple Choices 300 error with my old configuration.. it has something to do with updating PHP to version v5.4.16 or higher.

How long does it take for .htaccess changes to take effect?

I have added url rewrite rules to my .htaccess file. Should I see these changes working right away?
Changes to .htaccess are immediate and do not require a restart. Normally, if you aren't seeing what you expect from .htaccess changes, you have a syntax error and should check Apache's logs for some idea of what's going on.
If you use redirect 301, clear browser cache.
NVM found it.
The .htaccess files follow the same syntax as the main configuration
files. Since .htaccess files are read on every request, changes made
in these files take immediate effect.
Apparently, some servers only check .htaccess files periodically. I've found this to be the case w/ our AWS host.
My source is only a comment below the answer here, but it matches my experiences and others seem to agree.

Updating Files on Apache

I'm having trouble with my Apache Web Server. I have a folder (htdocs\images) where I have a number of images already in place. I can browse them and see them on my web server (and access them via HTML). I added a new image in there today, and went to browse to it, and it can't be found. I double and triple checked the path and everything. I even restarted Apache and that didn't seem to help.
I'm really confused as to what's going on here. Anybody have any suggestions?
Thank you.
Edit I just turned on the ability for the images directory to be listed, browsed to it (http://127.0.0.1/images/) and I was able to see all the previous images that were in the folder, but not the new one.
Turn directory indexes on for htdocs\images, remove (or move out of the way) any index.* files, and point your browser at http://yoursite/images/
That should give you a full listing of files in that directory. If the file you're looking for isn't there, then Apache is looking at a different directory than you think it is. You'll have to search your httpd.conf for clues -- DocumentRoot, Alias, AliasMatch, Redirect, RedirectMatch, RewriteRule -- there are probably dozens of apache directives that could be causing the web server to get its documents from somewhere other than where you think it's looking.
make sure the caSE and spelling are 100% correct.
There is not magic in programming (some may disagree:), so look for silly errors. Wrong server? Case of your letters? Wrong extension?
There's a chance it could be due to the cookies stored on your device. I would delete all cookies to the website you're working on before you refresh again