Invision Community 4: SEO, prepare for v5 and dormant account notifications By Matt Monday at 02:04 PM
OctoDev Posted January 28, 2019 Posted January 28, 2019 Why are the emergency / bug fixes breaking themes? It makes no sense. I thought they were strictly patches, not something that would ruin the custom theme.
Stuart Silvester Posted January 28, 2019 Posted January 28, 2019 We haven't recently released any patches or minor updates for 4.3.6. We have however released 4.4 Beta 1 today, is it possible that you've upgraded to the beta (which may cause incompatibilities in your custom themes)
Pete T Posted January 28, 2019 Posted January 28, 2019 9 minutes ago, Stuart Silvester said: We haven't recently released any patches or minor updates for 4.3.6. We have however released 4.4 Beta 1 today, is it possible that you've upgraded to the beta (which may cause incompatibilities in your custom themes) 13 minutes ago, Jimmy Gavekort said: Why are the emergency / bug fixes breaking themes? It makes no sense. I thought they were strictly patches, not something that would ruin the custom theme. this because 4.4.0 has changed few templates the first will be globaltemplate the lkeywarning not in this template any more but i would wait to finial before upgrading live site.
Ramsesx Posted January 28, 2019 Posted January 28, 2019 29 minutes ago, Stuart Silvester said: We haven't recently released any patches or minor updates for 4.3.6. We have however released 4.4 Beta 1 today, is it possible that you've upgraded to the beta (which may cause incompatibilities in your custom themes) Guess he means this:
Pete T Posted January 28, 2019 Posted January 28, 2019 4 minutes ago, Ramsesx said: Guess he means this: yeah but it only displays if have this define( 'USE_DEVELOPMENT_BUILDS', TRUE ); in constants.php but even if was displaying normal any dev would take few hours to check what new and see if needs updating but many wait to finial.
Ramsesx Posted January 28, 2019 Posted January 28, 2019 3 minutes ago, Pete T said: yeah but it only displays if have this define( 'USE_DEVELOPMENT_BUILDS', TRUE ); in constants.php but even if was displaying normal any dev would take few hours to check what new and see if needs updating but many wait to finial. Sure, but the part "and includes a security patch" may lead some people doing a mistake. There could be an additional line "don't upgrade your live board, only for testing purposes" or similar.
Pete T Posted January 28, 2019 Posted January 28, 2019 1 minute ago, Ramsesx said: Sure, but the part "and includes a security patch" may lead some people doing a mistake. There could be an additional line "don't upgrade your live board, only for testing purposes" or similar. agree there as sure if was security patch and that bad should been added in 4.3.6 in patch we can run via visiting support tool.
Stuart Silvester Posted January 28, 2019 Posted January 28, 2019 What's happening there is that you weren't using the 'latest' version of 4.3.6, the update check is seeing that and including a 4.3.6 version as an available upgrade. We'll look at improving that. I'd like to remind you that you'll only see this if you have opted into receiving beta updates, if you do not want them you should remove define( 'USE_DEVELOPMENT_BUILDS', TRUE ); from your constants.php
Joel R Posted January 28, 2019 Posted January 28, 2019 1. Did you download 4.4 Beta1? 2. Revert to default IPS theme 3. Send in an emergency ticket in Client Area
Pete T Posted January 28, 2019 Posted January 28, 2019 3 minutes ago, Joel R said: 1. Did you download 4.4 Beta1? 2. Revert to default IPS theme 3. Send in an emergency ticket in Client Area 1. yes he has download 4.4.0 beta 1 as seen error myself when view custom themes that i am working on update 2. i would say using default theme if updated live site. 3. it not reply emergency ticket he needs as site is view able he needs do to remove the define( 'USE_DEVELOPMENT_BUILDS', TRUE ); or added define( 'USE_DEVELOPMENT_BUILDS', FALSE );
OctoDev Posted January 28, 2019 Author Posted January 28, 2019 2 hours ago, Stuart Silvester said: What's happening there is that you weren't using the 'latest' version of 4.3.6, the update check is seeing that and including a 4.3.6 version as an available upgrade. We'll look at improving that. I'd like to remind you that you'll only see this if you have opted into receiving beta updates, if you do not want them you should remove define( 'USE_DEVELOPMENT_BUILDS', TRUE ); from your constants.php faeces, yeah that was enabled. I was only paying attention to the red alert, security warning which led me to patching it ASAP.
Recommended Posts
Archived
This topic is now archived and is closed to further replies.