Textpattern CMS support forum

You are not logged in. Register | Login | Help

#21 2012-09-17 13:08:53

Bloke
Developer
From: Leeds, UK
Registered: 2006-01-29
Posts: 8,605
Website

Re: Feedback to: Textpattern CMS 4.5.1 released

miles wrote:

Everytime I try to edit an article I get “Sorry, the form could not be submitted. Please try again later.”

Have you recently upgraded? If so, my first port of call would be to ensure you’ve flushed your browser cache / forced an admin-side page load? It may be serving a stale copy of textpattern.js, for example.


The smd plugin menagerie — for when you need one more gribble of power from Textpattern. Bleeding-edge code available on GitHub.

Txp Builders – finely-crafted code, design and Txp

Offline

#22 2012-09-17 13:20:02

maniqui
Moderator
From: Buenos Aires, Argentina
Registered: 2004-10-10
Posts: 3,070
Website

Re: Feedback to: Textpattern CMS 4.5.1 released

miles wrote:

Guys, Everytime I try to edit an article I get “Sorry, the form could not be submitted. Please try again later.”
Any thoughts on why this is happening?

It could be a plugin interfering there (it happened to me).
Try disabling plugins (particularly, those that are loaded in or affect the Write tab).

In any case, even if you get that “Sorry…” message, the content gets saved properly in the DB (well, at least, in my case, that’s what happened).


La música ideas portará y siempre continuará

TXP Builders – finely-crafted code, design and txp

Offline

#23 2012-09-17 13:28:52

miles
Member
From: Plymouth
Registered: 2008-05-22
Posts: 73
Website

Re: Feedback to: Textpattern CMS 4.5.1 released

Bloke wrote:

miles wrote:

Everytime I try to edit an article I get “Sorry, the form could not be submitted. Please try again later.”

Have you recently upgraded? If so, my first port of call would be to ensure you’ve flushed your browser cache / forced an admin-side page load? It may be serving a stale copy of textpattern.js, for example.

Tried everything mate. I have had to go back to 4.4.1

Offline

#24 2012-09-17 13:50:51

Bloke
Developer
From: Leeds, UK
Registered: 2006-01-29
Posts: 8,605
Website

Re: Feedback to: Textpattern CMS 4.5.1 released

miles wrote:

Tried everything mate.

I figured you’d have done that already, ‘twas just a long shot.

In which case I’d go with maniqui and say it’s plugin interference. As well as the msd_minibar thing raised in the post linked above, glz_custom_fields is known to cause similar things. You can try shutting plugins off one by one to find the culprit(s) then bend the plugin author’s ear (it may be me, gulp!)

The wet_plugout plugin can help track down such things.


The smd plugin menagerie — for when you need one more gribble of power from Textpattern. Bleeding-edge code available on GitHub.

Txp Builders – finely-crafted code, design and Txp

Offline

#25 2012-09-18 02:59:42

gomedia
Plugin Author
Registered: 2008-06-01
Posts: 1,225
Website

Re: Feedback to: Textpattern CMS 4.5.1 released

I’m gradually working my way through the various adi_plugins to make them TXP 4.5 friendly and I’ve hit a snag with lifecycle events.

In the old days (i.e. pre 4.5), when a plugin was uploaded the “installed” lifecycle event would fire. Then the plugin had to be made active & the “enabled” event would kick in. This was the case whether it was a new plugin or a new version of an existing one.

Now, on TXP 4.5, it seems that if the plugin is already installed & active, then the new version doesn’t have to be made active manually.

The problem I’m now seeing is that, in this case, the “installed” event fires but not the “enabled” one – which is affecting how the plugin behaves during installation.

Is this new lifecycle behaviour intended?

Offline

#26 2012-09-18 04:04:07

wet
Developer
From: Lenzing, Austria
Registered: 2005-06-06
Posts: 3,267
Website

Re: Feedback to: Textpattern CMS 4.5.1 released

It is intentional but may have consequences for your particular use case that we didn’t think of. As in previous versions “enabled” is fired when a plugin is enabled. How were you using this specific sequence of events? Would an additional “updated” event be helpful?

Offline

#27 2012-09-18 04:28:29

gomedia
Plugin Author
Registered: 2008-06-01
Posts: 1,225
Website

Re: Feedback to: Textpattern CMS 4.5.1 released

This is how I’ve been using the lifecycle events:

installed – do nothing
enabled – create db tables, upgrade db table structure, set prefs etc
disabled – do nothing
deleted – drop tables, delete prefs

The logic being that:

  • uploading a plugin but not making it active (“installed”) shouldn’t do anything drastic
  • making a plugin active (“enabled”) should set everything up
  • making a plugin inactive (“disabled”) should only stop it from running
  • deleting a plugin (“deleted”) should tidy everything up

Unfortunately, now that the “enabled” event is not firing during a plugin re-upload none of my upgrade functions are happening.

An “upgraded” event may be useful. But in the meantime, maybe I need to do a check during “installed” to see if the plugin has been installed previously & automatically run the “enabled” routines?

Last edited by gomedia (2012-09-18 04:29:20)

Offline

#28 2012-09-18 04:35:20

wet
Developer
From: Lenzing, Austria
Registered: 2005-06-06
Posts: 3,267
Website

Re: Feedback to: Textpattern CMS 4.5.1 released

gomedia wrote:

maybe I need to do a check during “installed” to see if the plugin has been installed previously & automatically run the “enabled” routines?

Sounds reasonable. Some people use the four high bits of the ‘flags’ column in txp_plugins to track private states. Please not that the lower 12 bits are reserved for core.

Offline

#29 2012-09-23 12:15:46

linguist
Member
Registered: 2007-11-03
Posts: 24

Re: Feedback to: Textpattern CMS 4.5.1 released

Hello! My web developer upgraded my Textpattern 4.4.1 to 4.5.1 yesterday, and everything seems fine. My sincere gratitude to Textpattern developers.

I have one question. Sometimes I check “Forgot password” mechanism by typing in a random name (not any of the users’ name, and no e-mail for it in the Admin panel) and clicking “Reset password”, just to check that everything works as expected. In previous versions, Textpattern responded with “Unknown author”, and that was all.

But Textpattern 4.5.1 responded by showing this message: “A confirmation message was sent to your e-mail address. Please visit your inbox and follow the instructions.” I’m a little worried. I’d like to know if this is expected behavior. Is there any chance that Textpattern did send a message somewhere? (No message in any of my users’ e-mail boxes.) Or is it just some kind of general message for error cases with “Forgot password”? Thank you.

Offline

#30 2012-09-23 13:23:32

Gocom
Plugin Author
From: Helsinki, Finland
Registered: 2006-07-14
Posts: 4,526
Website

Re: Feedback to: Textpattern CMS 4.5.1 released

linguist wrote:

But Textpattern 4.5.1 responded by showing this message: “A confirmation message was sent to your e-mail address. Please visit your inbox and follow the instructions.” I’m a little worried. I’d like to know if this is expected behavior. Is there any chance that Textpattern did send a message somewhere? (No message in any of my users’ e-mail boxes.) Or is it just some kind of general message for error cases with “Forgot password”? Thank you.

Everything works as expected, and no email is actually sent. Displaying the same success message is a security related feature and an improvement from 4.4.1.

Any public facing log-in or password recovery form should really never reveal whether a user account exists or not. Otherwise the form can be used to fish out and verify existing, real user accounts. This was what the reset form prior to 4.5.0 allowed to do.

Last edited by Gocom (2012-09-23 13:25:48)

Offline

Board footer

Powered by FluxBB