Textpattern CMS support forum
You are not logged in. Register | Login | Help
- Topics: Active | Unanswered
Re: wet_parachute: "Warn before close" for the content > write screen
Oh, I guess I can just safely update the value of $warning ?
Offline
#14 2009-09-26 16:32:38
- candyman
- Member
- From: Italy
- Registered: 2006-08-08
- Posts: 684
Re: wet_parachute: "Warn before close" for the content > write screen
Great plugin with an annoying, at least for me, behaviour.
If I enter in the admin area (which, by default, opens on “content > write” screen) and – for the first thing – try to change to another admin section (for example “extensions”) the “Are you sure?” pop-up appears…
Is there a way to avoid this alert if there are absolutely no words in the message body?
Last edited by candyman (2009-09-27 09:25:16)
Offline
#15 2009-10-04 12:00:58
- candyman
- Member
- From: Italy
- Registered: 2006-08-08
- Posts: 684
Re: wet_parachute: "Warn before close" for the content > write screen
Robert, no solution for the behaviour I’ve found?
Thanks in advance.
Last edited by candyman (2009-10-04 12:06:31)
Offline
Re: wet_parachute: "Warn before close" for the content > write screen
Great plugin with an annoying, at least for me, behaviour.
If I enter in the admin area (which, by default, opens on “content > write” screen) and – for the first thing – try to change to another admin section (for example “extensions”) the “Are you sure?” pop-up appears…
Is there a way to avoid this alert if there are absolutely no words in the message body?
Like Candyman, I find this behaviour very annoying.
Offline
Re: wet_parachute: "Warn before close" for the content > write screen
PascalL wrote:
Like Candyman, I find this behaviour very annoying.
You can change the default page after login into textpattern
go to Admin > Advanced > default_event:
change it to other page, I think changing it to the Articles page will be nice and comfortable for the client.
Offline
Re: wet_parachute: "Warn before close" for the content > write screen
I have the same problem as a few folks above. The popup pops up even when no changes are made. Not every time, but often enough to be more annoying than helpful.
Last edited by floodfish (2010-04-08 22:53:18)
Offline
#19 2011-05-25 23:51:13
- Leonick
- Member
- Registered: 2007-07-30
- Posts: 16
Re: wet_parachute: "Warn before close" for the content > write screen
Does this problem comes just with tinymce plugin ?
in this case, I can solve the problem
Offline
Re: wet_parachute: "Warn before close" for the content > write screen
PHP warning report:
Deprecated: Function split() is deprecated in /path/to/textpattern/lib/txplib_misc.phpWhen I disable wet_parachute, the warning goes away.
Offline
Re: wet_parachute: "Warn before close" for the content > write screen
Very strange. There’s no occurrence of PHP’s split() in wet_parachute 0.7.
Offline
Re: wet_parachute: "Warn before close" for the content > write screen
Indeed! I accidentally deleted mine before looking at the version number, as soon as I found out that making it inactive got rid of the notice. When I upload the latest version, there’s no warning.
Offline
#23 2012-08-24 04:16:55
- fastasleep
- Member
- Registered: 2008-06-17
- Posts: 10
Re: wet_parachute: "Warn before close" for the content > write screen
How? I am having this problem with wet_parachute and hak_tinymce, would love to fix it. Thanks!
Leonick wrote:
Does this problem comes just with tinymce plugin ?
in this case, I can solve the problem
Offline
#24 2012-08-28 00:43:32
- fastasleep
- Member
- Registered: 2008-06-17
- Posts: 10
Re: wet_parachute: "Warn before close" for the content > write screen
Anyone have any ideas about how to avoid TinyMCE from causing this plugin to trigger every time you leave the page (whether you’ve edited anything or not)?
OR alternately, is there another WYSIWYG editor I can install that doesn’t conflict with this?
Thanks!
fastasleep wrote:
How? I am having this problem with wet_parachute and hak_tinymce, would love to fix it. Thanks!
Leonick wrote:
Does this problem comes just with tinymce plugin ?
in this case, I can solve the problem
Offline