We use cookies to improve your experience. No personal information is gathered and we don't serve ads. Cookies Policy.

ExpressionEngine Logo ExpressionEngine
Features Pricing Support Find A Developer
Partners Upgrades
Blog Add-Ons Learn
Docs Forums University
Log In or Sign Up
Log In Sign Up
ExpressionEngine Logo
Features Pro new Support Find A Developer
Partners Upgrades
Blog Add-Ons Learn
Docs Forums University Blog
  • Home
  • Forums

Extensions fail to receive submit_new_entry(_x) calls - Quick Save returns prematurely

Development and Programming

Erik Stainsby's avatar
Erik Stainsby
9 posts
17 years ago
Erik Stainsby's avatar Erik Stainsby

I believe that the Quick Save return call should be repositioned to allow for the submit_new_entry(_x) hooks to be honoured. At present any extension waiting for such a hook will never receive it is the user consistently prefers quick save (which sounds quicker, don’t it?)

I have an extension which is expecting to update my own tables with the (newly generated) entry_id.

I’m not alone in being caught up by this “misfeature”: reference: http://ellislab.com/forums/viewthread/70754/

Hope this can be addressed in a patch (?) Currently running 1.6.4

Regards, Erik

       
Tim Smith's avatar
Tim Smith
15 posts
16 years ago
Tim Smith's avatar Tim Smith

I agree this is a bug.

As it stands extensions that need to write any data cannot be made compatible with the Quick Save feature. I was looking into tweaking this so that Quick Save could work but it returns from the code before any usable hook.

       
Tim Smith's avatar
Tim Smith
15 posts
16 years ago
Tim Smith's avatar Tim Smith

Raised in bug forum here

       

Reply

Sign In To Reply

ExpressionEngine Home Features Pro Contact Version Support
Learn Docs University Forums
Resources Support Add-Ons Partners Blog
Privacy Terms Trademark Use License

Packet Tide owns and develops ExpressionEngine. © Packet Tide, All Rights Reserved.