Jump to content

Davyc

Clients
  • Posts

    1,326
  • Joined

  • Days Won

    18

Reputation Activity

  1. Like
    Davyc got a reaction from Hisashi in IPS 4.7.2 final major problem   
    The devil is in the detail, as is said.  The detail, however was assumed that everyone was on board and up-to-date.  I would still have liked to have seen a warning about third party apps possibly being locked 'before' the upgrade began.  It does this with themes where you either proceed or cancel the upgrade.  Running a scan after the fact is assuming a lot from people.
    I agree wholeheartedly that if your site is mission critical then you should test 'every' update, not just this one, before proceeding to save yourself a lot of heartache.
    As far as information, blogs, etc, not everyone reads them, especially if they are aimed at devs.  Even a post telling people be warned that some/all of your apps will be locked, so check with the devs to make sure they are up-to-date.
    I would even go as far as flagging all apps in the marketplace to show that they are compatible with 4.7.2 because the 4.7 compatible flag may not always be correct, as witness in my own case where the apps are still purchasable, but will not work in 4.7.2 at this point in time. 
    There's a lot more that could have been done to inform people of the pitfalls in an unmistakeable way - a pre-upgrade warning would have put me off upgrading until I was sure that everything would work, I never dreamed that some of the apps I use would be locked.
    There are plusses and minuses in all of this; the good, the bad and the ugly if you wish lol.
    As I mentioned it's no big deal to me, because I'm just a hobbyist, but someone else may have an even bigger headache to contend with.  Fair play to IPS for moving things forward and creating a great environment for us all to play and work with, but information is thin on the ground and I believe that is the one weakness that needs addressing 🙂
     
  2. Like
    Davyc got a reaction from LiquidFractal in IPS 4.7.2 final major problem   
    That is the issue @Matt these apps 'are' 4.7 compatible and they are in the marketplace.  I've received a reply from the author who has provided replacement files and the support page now shows no errors at all, but the app is still locked.
     
     
     
  3. Like
    Davyc got a reaction from Luke Z in IPS 4.7.2 final major problem   
    I've contacted the author, but my issue is not with something that needs to be corrected, rather it is that this information was provided 'after the upgrade' had that warning appeared prior then I would have contacted the author and waited for a solution before updating.  I'm now at the mercy of the app provided to discover the issue, correct it/them and provide and update to the marketplace where it will be queued for approval.  
    I'm wondering how many apps will fall under this lock out as the apps are still available in the marketplace and they can still be installed from the ACP.  There should have been a warning prior to upgrade to prevent clients sites from being rendered inoperable.
  4. Thanks
    Davyc reacted to Stuart Silvester in IPS 4.7.2 - sys. errors log   
    You can safely ignore that log if you don't have Commerce installed. Our logging is a bit verbose for this version so we have extra diagnostic information if needed and we'll be scaling some of that back in future releases.
  5. Thanks
    Davyc reacted to Matt in 4.7.2 PHP 8 Compatibility Scanner [Please read if upgrading from 4.7.1 or below]   
    Invision Community 4.7.2 now features a third party application and plug-ins PHP 8 compatibility scanner.
    Please read this post as you may find applications of plugins disabled after upgrading.
    Why do we need this?
    The underlying programming language that Invision Community uses is PHP. The latest version, PHP 8 was released in November 2020 and features many breaking changes and incompatibilities that are not backwards compatible. Some of these changes mean that what was a harmless silent notice, is now a fatal error which would mean that if you upgrade with incompatible code, your community would throw a fatal error which results in either a white screen, or a server level error message in your browser.
    These fatal errors cannot be captured by Invision Community and managed. The fatal errors are deeper in the execution chain.
    PHP 8 has been out for close to two years, and PHP 7.4 is 'end of life' and security updates will cease from November which means that it becomes insecure, so everyone will have to move to PHP 8 very shortly.
    What is it
    The compatibility checker examines all third party applications and plugins that you have added from the Marketplace.
    We encourage our Marketplace authors to test with PHP 8 but not all do, and as such applications and plugins that work fine with PHP 7.4 will fail with PHP 8.
    The compatibility checker scans all third party code for issues that could cause fatal errors, and if it finds them it will disable the application or plugin on upgrade.
    The only way to re-enable the application or upgrade is to update it to a 4.7.2 compatible version from the marketplace.
    Can I re-enable disabled third party plugins and applications?
    Yes, if you are confident the plugins and applications are fine to run with your current PHP version then you can re-enable them until our November release which will then enforce the disabling of applications.

    It's worth reaching out to the authors of key plugins and applications to see if they have a PHP8 compatible version available, or plan to have one by November so you can prepare for the November upgrade.
    Is this really needed?
    Unfortunately yes. PHP are making bold changes that are not backwards compatible. Invision Community is fortunate to have so many third party developers releasing apps and plugins to further enhance the feature-set, but we do not have direct control over this code. Our priority is to ensure that your site upgrades smoothly and remains online.
    Why now?
    We finally ran out of road. We have been working towards PHP 8 compatibility for a while, and we have encouraged our third party authors to do so too, and to test with PHP 8. We also informed the developers in August about the scanner and what it may do to their applications. We also have been releasing Invision Community 4.7 betas since May of this year to give them as much time as possible to update their applications. Enforcing this change is painful in the short term but benefits everyone in the longer term.
    What else can I do?
    Your self-hosting license allows you a test install which you should use as a staging site and test any upgrades on that staging site before performing the upgrade on your production site. This will enable you to capture any issues that may arise before you run it on your production site.

    As always, we recommend that a back-up snapshot is taken before any upgrade so that you can easily rollback if you encounter any issues.
    I'm using PHP 7, does this affect me?
    Yes, the compatibility scanner will still run on the upgrade and check for PHP 8 issues so that when you do upgrade to PHP 8 you won't find that your community is no longer working.

    Thanks for reading!
  6. Agree
    Davyc reacted to Adriano Faria in IPS 4.7.2 final major problem   
    Another suggestion, @Matt.
     Make this message visible to everyone:

     
    Transparency never hurts and will certainly avoid posts and messages asking to update.
    Currently it shows only to file submitter (and staff).
  7. Like
    Davyc got a reaction from DamonT in IPS 4.7.2 final major problem   
    I've contacted the author, but my issue is not with something that needs to be corrected, rather it is that this information was provided 'after the upgrade' had that warning appeared prior then I would have contacted the author and waited for a solution before updating.  I'm now at the mercy of the app provided to discover the issue, correct it/them and provide and update to the marketplace where it will be queued for approval.  
    I'm wondering how many apps will fall under this lock out as the apps are still available in the marketplace and they can still be installed from the ACP.  There should have been a warning prior to upgrade to prevent clients sites from being rendered inoperable.
  8. Like
    Davyc got a reaction from SeNioR- in IPS 4.7.2 final major problem   
    Just a very quick update before I sign off for the evening.  @Adriano Faria has pulled it out of the bag and the app that I use that is crucial to my site's existence has been swiftly approved in the Marketplace and my site is back up and running now.  So, a huge thankyou to @Adriano Faria and a big thank you to IPS for expediting the approval of the app.
    I would point out one small thing to anyone who has a similar experience, once you update you have to 'enable' the app in the applications section of the ACP as it is not automatically enabled.  The locked status is no longer present.
    Hope that helps 🙂
     
  9. Like
    Davyc got a reaction from SeNioR- in IPS 4.7.2 final major problem   
    The devil is in the detail, as is said.  The detail, however was assumed that everyone was on board and up-to-date.  I would still have liked to have seen a warning about third party apps possibly being locked 'before' the upgrade began.  It does this with themes where you either proceed or cancel the upgrade.  Running a scan after the fact is assuming a lot from people.
    I agree wholeheartedly that if your site is mission critical then you should test 'every' update, not just this one, before proceeding to save yourself a lot of heartache.
    As far as information, blogs, etc, not everyone reads them, especially if they are aimed at devs.  Even a post telling people be warned that some/all of your apps will be locked, so check with the devs to make sure they are up-to-date.
    I would even go as far as flagging all apps in the marketplace to show that they are compatible with 4.7.2 because the 4.7 compatible flag may not always be correct, as witness in my own case where the apps are still purchasable, but will not work in 4.7.2 at this point in time. 
    There's a lot more that could have been done to inform people of the pitfalls in an unmistakeable way - a pre-upgrade warning would have put me off upgrading until I was sure that everything would work, I never dreamed that some of the apps I use would be locked.
    There are plusses and minuses in all of this; the good, the bad and the ugly if you wish lol.
    As I mentioned it's no big deal to me, because I'm just a hobbyist, but someone else may have an even bigger headache to contend with.  Fair play to IPS for moving things forward and creating a great environment for us all to play and work with, but information is thin on the ground and I believe that is the one weakness that needs addressing 🙂
     
  10. Agree
    Davyc got a reaction from OptimusBain in IPS 4.7.2 final major problem   
    Thanks @Adriano Faria you are on the ball and even though you provided me with the two files that were causing the issue, the app remains locked.  So I will have to wait until the new version is approved.
    To IPS I would say that you really need to inform people that some/all of their apps, even though they are Marketplace validated for 4.7 may cease to function because of these issues.  Some kind of pre-upgrade check should be made, rather than waiting until after the fact which then puts pressure on developers to update their apps and then get them into the Marketplace.  In this instance I would advise a more swift approval of affected apps so your clients sites are not rendered inoperable, which is an incredibly frustrating issue.
  11. Like
    Davyc got a reaction from Luke Z in IPS 4.7.2 final major problem   
    That is the issue @Matt these apps 'are' 4.7 compatible and they are in the marketplace.  I've received a reply from the author who has provided replacement files and the support page now shows no errors at all, but the app is still locked.
     
     
     
  12. Like
    Davyc got a reaction from OptimusBain in IPS 4.7.2 final major problem   
    I'm curious to know why information regarding certain plugins was not checked before the upgrade began.  I have two applications that have now been 'locked' because of some PHP 8 incompatibilities.  My site is now completely crippled because the app that is locked is the mainstay of the site.  As it stands my site is now useless.  Had the below warning appeared prior to upgrade I would not have proceeded.

  13. Like
    Davyc got a reaction from AlexJ in IPS 4.7.2 final major problem   
    The devil is in the detail, as is said.  The detail, however was assumed that everyone was on board and up-to-date.  I would still have liked to have seen a warning about third party apps possibly being locked 'before' the upgrade began.  It does this with themes where you either proceed or cancel the upgrade.  Running a scan after the fact is assuming a lot from people.
    I agree wholeheartedly that if your site is mission critical then you should test 'every' update, not just this one, before proceeding to save yourself a lot of heartache.
    As far as information, blogs, etc, not everyone reads them, especially if they are aimed at devs.  Even a post telling people be warned that some/all of your apps will be locked, so check with the devs to make sure they are up-to-date.
    I would even go as far as flagging all apps in the marketplace to show that they are compatible with 4.7.2 because the 4.7 compatible flag may not always be correct, as witness in my own case where the apps are still purchasable, but will not work in 4.7.2 at this point in time. 
    There's a lot more that could have been done to inform people of the pitfalls in an unmistakeable way - a pre-upgrade warning would have put me off upgrading until I was sure that everything would work, I never dreamed that some of the apps I use would be locked.
    There are plusses and minuses in all of this; the good, the bad and the ugly if you wish lol.
    As I mentioned it's no big deal to me, because I'm just a hobbyist, but someone else may have an even bigger headache to contend with.  Fair play to IPS for moving things forward and creating a great environment for us all to play and work with, but information is thin on the ground and I believe that is the one weakness that needs addressing 🙂
     
  14. Like
    Davyc got a reaction from OptimusBain in IPS 4.7.2 final major problem   
    That is the issue @Matt these apps 'are' 4.7 compatible and they are in the marketplace.  I've received a reply from the author who has provided replacement files and the support page now shows no errors at all, but the app is still locked.
     
     
     
  15. Like
    Davyc got a reaction from AlexJ in IPS 4.7.2 final major problem   
    That is the issue @Matt these apps 'are' 4.7 compatible and they are in the marketplace.  I've received a reply from the author who has provided replacement files and the support page now shows no errors at all, but the app is still locked.
     
     
     
  16. Like
    Davyc got a reaction from a Chunk in IPS 4.7.2 final major problem   
    I've contacted the author, but my issue is not with something that needs to be corrected, rather it is that this information was provided 'after the upgrade' had that warning appeared prior then I would have contacted the author and waited for a solution before updating.  I'm now at the mercy of the app provided to discover the issue, correct it/them and provide and update to the marketplace where it will be queued for approval.  
    I'm wondering how many apps will fall under this lock out as the apps are still available in the marketplace and they can still be installed from the ACP.  There should have been a warning prior to upgrade to prevent clients sites from being rendered inoperable.
  17. Like
    Davyc got a reaction from a Chunk in IPS 4.7.2 final major problem   
    I'm curious to know why information regarding certain plugins was not checked before the upgrade began.  I have two applications that have now been 'locked' because of some PHP 8 incompatibilities.  My site is now completely crippled because the app that is locked is the mainstay of the site.  As it stands my site is now useless.  Had the below warning appeared prior to upgrade I would not have proceeded.

  18. Like
    Davyc got a reaction from CaliPilot in IPS 4.7.2 final major problem   
    Just a very quick update before I sign off for the evening.  @Adriano Faria has pulled it out of the bag and the app that I use that is crucial to my site's existence has been swiftly approved in the Marketplace and my site is back up and running now.  So, a huge thankyou to @Adriano Faria and a big thank you to IPS for expediting the approval of the app.
    I would point out one small thing to anyone who has a similar experience, once you update you have to 'enable' the app in the applications section of the ACP as it is not automatically enabled.  The locked status is no longer present.
    Hope that helps 🙂
     
  19. Like
    Davyc got a reaction from CaliPilot in IPS 4.7.2 final major problem   
    The devil is in the detail, as is said.  The detail, however was assumed that everyone was on board and up-to-date.  I would still have liked to have seen a warning about third party apps possibly being locked 'before' the upgrade began.  It does this with themes where you either proceed or cancel the upgrade.  Running a scan after the fact is assuming a lot from people.
    I agree wholeheartedly that if your site is mission critical then you should test 'every' update, not just this one, before proceeding to save yourself a lot of heartache.
    As far as information, blogs, etc, not everyone reads them, especially if they are aimed at devs.  Even a post telling people be warned that some/all of your apps will be locked, so check with the devs to make sure they are up-to-date.
    I would even go as far as flagging all apps in the marketplace to show that they are compatible with 4.7.2 because the 4.7 compatible flag may not always be correct, as witness in my own case where the apps are still purchasable, but will not work in 4.7.2 at this point in time. 
    There's a lot more that could have been done to inform people of the pitfalls in an unmistakeable way - a pre-upgrade warning would have put me off upgrading until I was sure that everything would work, I never dreamed that some of the apps I use would be locked.
    There are plusses and minuses in all of this; the good, the bad and the ugly if you wish lol.
    As I mentioned it's no big deal to me, because I'm just a hobbyist, but someone else may have an even bigger headache to contend with.  Fair play to IPS for moving things forward and creating a great environment for us all to play and work with, but information is thin on the ground and I believe that is the one weakness that needs addressing 🙂
     
  20. Like
    Davyc got a reaction from Giray in IPS 4.7.2 final major problem   
    Just a very quick update before I sign off for the evening.  @Adriano Faria has pulled it out of the bag and the app that I use that is crucial to my site's existence has been swiftly approved in the Marketplace and my site is back up and running now.  So, a huge thankyou to @Adriano Faria and a big thank you to IPS for expediting the approval of the app.
    I would point out one small thing to anyone who has a similar experience, once you update you have to 'enable' the app in the applications section of the ACP as it is not automatically enabled.  The locked status is no longer present.
    Hope that helps 🙂
     
  21. Like
    Davyc got a reaction from Martin A. in IPS 4.7.2 final major problem   
    The devil is in the detail, as is said.  The detail, however was assumed that everyone was on board and up-to-date.  I would still have liked to have seen a warning about third party apps possibly being locked 'before' the upgrade began.  It does this with themes where you either proceed or cancel the upgrade.  Running a scan after the fact is assuming a lot from people.
    I agree wholeheartedly that if your site is mission critical then you should test 'every' update, not just this one, before proceeding to save yourself a lot of heartache.
    As far as information, blogs, etc, not everyone reads them, especially if they are aimed at devs.  Even a post telling people be warned that some/all of your apps will be locked, so check with the devs to make sure they are up-to-date.
    I would even go as far as flagging all apps in the marketplace to show that they are compatible with 4.7.2 because the 4.7 compatible flag may not always be correct, as witness in my own case where the apps are still purchasable, but will not work in 4.7.2 at this point in time. 
    There's a lot more that could have been done to inform people of the pitfalls in an unmistakeable way - a pre-upgrade warning would have put me off upgrading until I was sure that everything would work, I never dreamed that some of the apps I use would be locked.
    There are plusses and minuses in all of this; the good, the bad and the ugly if you wish lol.
    As I mentioned it's no big deal to me, because I'm just a hobbyist, but someone else may have an even bigger headache to contend with.  Fair play to IPS for moving things forward and creating a great environment for us all to play and work with, but information is thin on the ground and I believe that is the one weakness that needs addressing 🙂
     
  22. Like
    Davyc got a reaction from Martin A. in IPS 4.7.2 final major problem   
    Just a very quick update before I sign off for the evening.  @Adriano Faria has pulled it out of the bag and the app that I use that is crucial to my site's existence has been swiftly approved in the Marketplace and my site is back up and running now.  So, a huge thankyou to @Adriano Faria and a big thank you to IPS for expediting the approval of the app.
    I would point out one small thing to anyone who has a similar experience, once you update you have to 'enable' the app in the applications section of the ACP as it is not automatically enabled.  The locked status is no longer present.
    Hope that helps 🙂
     
  23. Thanks
    Davyc got a reaction from Adriano Faria in IPS 4.7.2 final major problem   
    Just a very quick update before I sign off for the evening.  @Adriano Faria has pulled it out of the bag and the app that I use that is crucial to my site's existence has been swiftly approved in the Marketplace and my site is back up and running now.  So, a huge thankyou to @Adriano Faria and a big thank you to IPS for expediting the approval of the app.
    I would point out one small thing to anyone who has a similar experience, once you update you have to 'enable' the app in the applications section of the ACP as it is not automatically enabled.  The locked status is no longer present.
    Hope that helps 🙂
     
  24. Agree
    Davyc reacted to Giray in IPS 4.7.2 final major problem   
    One more thing. A quick shout out to @Adriano Faria who first thing this morning, and I mean first thing, was hammering out update notices on all of his apps. He's the only one that I've seen all day. I hope they all get approved quickly, but kudos for the immediate intervention. I hope that the other devs are also pushing updates, especially on the big apps that so many of us use!
  25. Agree
    Davyc reacted to Giray in IPS 4.7.2 final major problem   
    Not sure if you notified all the third party devs but if they had been they would not be scrambling at the last minute. In a perfect world, for such a major shift, you'd think that third party developers would have upgraded their apps BEFORE 4.7.2 was released.
    Not looking for an answer or explanation inasmuch as what's done is done, but it would have been smoother.
×
×
  • Create New...