Chrome has this annoying prompt for reposting POST-forms.
While the idea of preventinmg double posts is nice, it doesn't make always sense since not every POST-form posts data in a forum or buys stuff in a webshop.
But Chrome has no option to disable this annoying behaviour.
Cannot "undo":
I have a POST-form where you can beautify text (sent via POST, returns beautified text). Sometimes it makes mistakes and you want to "undo" the submission so you go back in teh browser, but no! Chrome f***s you up with its annoying repost error message.
I cannot use GET since my form text is very long so i get the "URI too long" error.
How can this be fixed?
In the past the command line switch -disable-prompt-on-repost seemed to work, but that's no solution anyway since I cannot tell all my users to do this in order to use my website.
To my joy this morning, this appears to be removed (the popup when re-posting), I'm running version 29.0.1547.57. Not sure when it was removed.
However, I'm sure you redesigned your code/site long ago.
Related
I would like to use magnific popup for a site which is still in development, but unfortunately nothing happens after the installation and adding the static content in my template.
No matter what i try no popup comes up.
If someone would like to help me i will provide access to the site.
Thanks a lot!
First thing to do:
look at your source code: does the 'link' show any sign of 'magnific popup' code?
Added classes? id?
Second: do you see any extra javascript and/or stylesheet that is added by the extension?
If you answer negative to 1 of these, the extension does not output anything. Sounds logic, but it is the first step. Is it a solution? Nope, it means your live just got a bit more worse, but hang in there !
If it does show any code from the ext: look at your console, are there any js errors occurred ? (if you don't know what console is, or (even worse) you work with IE) please read about chrome console of at least install Firefox with firebug.
My best beth would be a JS error...
Can it be possible that the ext itself does not work?
Does your php error logs tell you that the extension is behaving badly?
Do you see errors in the typoscript analyser (or whatever it's called to analyse the css_styled_content and other TS spaghetti )
If not, then no, it is not the ext.
Again, i'm betting my wive, three horses and a barrel of beer on JS erros.
Good luck mate !
ps: IF i'm wrong, i'm not sending you my wife by postal service. Loads of trouble last time. Nor the horses, same shizzle ..
I have applications which are displayed as tabs in Facebook pages which have been working fine. They suddenly started displaying this output in the tab:
/1336720089,176820405/
if (window.CavalryLogger) { CavalryLogger.start_js(["EgxV3"]); }
__d("UFIUpdate",
Any ideas what is going on???
Here is a link to one of them: http://www.facebook.com/TweakShoes/app_132692060112327
A temporary solution is to add https:// to facebook itself. This doesn't solve the problem, but it'll allow you to see your page on a per client basis.
The best fix in the longer term until facebook fixes this issue is to go to your account settings > Security > Enable secure browsing. This will enforce HTTPS wherever it can and should resolve the issue for a lot of pages you're trying to access.
Good Luck!
After encountering this issue yesterday, I tracked it down to an apparent conflict with the JS log wrapper included as part of HTML5 Boilerplate's script.js file. In particular, the "make it safe to use console.log always" snippet. After commenting it out, the FB lib error went away and my app displayed properly.
I didn't dig into what the conflict was, but here is the snippet. If you use something similar on your page, then it may be worth investigating.
/* make it safe to use console.log always */
(function(b){function c(){}for(var d="assert,count,debug,dir,dirxml,error,exception,group,groupCollapsed,groupEnd,info,log,timeStamp,profile,profileEnd,time,timeEnd,trace,warn".split(","),a;a=d.pop();){b[a]=b[a]||c}})((function(){try
{console.log();return window.console;}catch(err){return window.console={};}})());
It's probably not a coincidence that FB's own logger bugs out with this.
Facebook has opened a bug for this issue and recently triaged it to medium priority - no word on when it will be addressed.
I've just submitted my first app to the App Store and I have problem with description field in iTunes Connect - it does not allow me to enter multiline value.
I've tried everything - copying-pasting from different editors, entering manually, etc.
If there is one line, like "Hello world" - it saves successfully.
When I've got at least 2 lines of text, lke
"Hello
World"
it just shows me the following error message and does not save:
Description cannot contain control characters (for example, null, new lines, carriage returns, escape, and other invisible characters).
Unbelievably this bug is back!
You can use Google Chrome, it's just broken in Safari.
Don't worry, this just started this morning, and is a bug that Apple has acknowledged. Hopefully this will be fixed soon. There are a lot of very unhappy people, me included, who can't get out important updates.
Posting this as an answer since I can't yet comment.
Not being able to enter multiline descriptions is an existing bug that only seems to occur sporadically. It is currently broken as of 8 hours ago on Chrome 51.0.2704.103 and Safari 9.1.1.
You can work around it by removing newlines, or waiting until Apple fixes the issue.
I'll report back when I see it fixed (I'm expecting the fix to take a day or two).
Edit: As of this morning, submitting to the App Store on Chrome with multiline descriptions is working!
I have 5 users (3 locations) using the pages that have Tiny_MCE text areas.
I receive No Errors and it works Perfectly on the other 4 machines running IE7 This would indicate there is No JavaScript Errors.
One user only is seeing the raw html code and no buttons at all.
I suspect it must be some IE setting that is wrong.
It does not appear that Javascript is disabled, as other Javascript functions work on that same site on the same machine in IE.
This user is running XP Pro, and IE 7.
When I installed FireFox on his machine, the Tiny_MCE works perfectly. This would Also indicate there is No JavaScript Errors.
I'm at a loss to explain it.
Any Ideas would be appreciated.
Thanks
Once I ran into same issue and the fix was to remove a comma at the end of the script. So check whether the error pattern is present in your code.
For example, the following code contains a bug which will prevent it from running in IE7.
tinyMCE.init({
// General options
mode: "textareas",
theme: "advanced",
...
template_replace_values: {
username: "Some User",
staffid: "991234"
}, // <<< BUG - Additional comma here
});
If you can enable javascript debugging in IE7 then post the js error here.
Funny thing. The problem fixed itself with no human assistance. No Reboot, No Nothing. after being AFU for 2 weeks, it just started working again.
Got to Love Windows!
I've encountered this before and it has always been a caching issue. Use Ctrl-F5 in IE to force a full refresh of the page and all its files (*.css, *.js) in the browser and the browser cache. My guess is the IE 7 computer that was bad had a 14 day setting for checking if files were up to date.
Sometimes it's been worse - the web server (tomcat 5.5) would cache the file too and not notice the file was updated. Restarting the web server fixed that.
We are experiencing the same problem with our software last few months.
I found this forum topic on developer's website:
http://tinymce.moxiecode.com/punbb/viewtopic.php?pid=66594
In short words, he is recommending to set strict_loading_mode to true when initializing tinymce. I've done that, and since that i had no problems.
I'm writing a selenium test for a GWT app. It uses the mouseover/
mousedown/mouseup approach to click pushbuttons. It clicks the Login
button of my app, which calls up the div containing userid and
password entry fields, and that works just fine. It then enters a userid and
password, then clicks the Submit button for the login form.
If I run it slowly, I can see the button click, but the request never
gets sent to the server (I'm watching the wire).
In fact, if, while the selenium IDE is still open, I manually click
the button, the request is not sent. If I then close the selenium IDE
and click the button, the request goes through fine.
Anybody seen this one? It seems really strange.
Update:
Firebug shows a script error. Apparently, the selenium script has some conflict with the GWT script. Here's the beginning of the error, but the whole thing is quite lengthy:
[Exception... "'com.google.gwt.core.client.JavaScriptException: (TypeError): result is null fileName: chrome://selenium-ide/content/recorder.js lineNumber: 74 stack: ([object XMLHttpRequest],"POST","http://localhost:8080/login",true)#chrome://selenium-ide/content/recorder.js:74 XPC_SJOW_CallWrapper((function (url, windowName, windowFeatures, replaceFlag) {if (self.openCalled) {return self.originalOpen.call(window, url, windowName, windowFeatures, replaceFlag);} else {self.o
Okay, I found the answer. It's a little embarrassing, but it provides the answer and it's funny, too. I'll share the answer so that you can avoid the problem, and perhaps have a laugh at my expense. :)
The answer is that you have to compile to OBF instead of PRETTY. All the associated links are listed below. They fully explain the problem, and how to avoid it.
What's funny about this? Well, as I was going through search, I finally hit upon the first link below. Almost immediately, I realized, or at least had a sneaking suspicion, that I had solved this problem before. Sure enough, the original question was posted in October, and I was the poster. So, I got an answer before, and completely forgot. Ah, well. Hope the answer helps someone, and my comic misfortune brightens your day.
http://clearspace.openqa.org/message/50170
http://groups.google.com/group/Google-Web-Toolkit/browse_thread/thread/5d6a9c448a82b916/af62e5877237b107?lnk=raot
http://code.google.com/p/google-web-toolkit/issues/detail?id=2861
Maybe you could try clickAt or mouseDownAt, they seem to perform a bit differently.