[Beta9.1] The V5 Pages=>Images widget (pagebuilderupload) can no longer be configured to show multiple images in the carousel as under V4

This one isnt a bug. Thats just the way it shows when you first add it to the page. However you can display it in many many different ways. Have a look at my response to someone on this here

https://invisioncommunity.com/forums/topic/480785-widgets/#findComment-2984729

Actually, with the Pages widget (not the gallery widget) there aren‘t any options besides autoplay. The Pages widget for images isn‘t configurable to show images like v4. 

Marc,

Thanks for your reply, but I believe that you are wrong...

Your response to someone else was with reference to "feeds" and they work differently. As your response to the someone else said, you can configure feeds in many different ways. The issue is that the pagebuilderupload widget does not work correctly and is not properly configurable in the way that you describe for feeds.

Of course, I get it that V5 is different. Let's consider two types of changes and the IMPACT ON DOWN TIME when I upgrade a live website...

1. Changes which require code changes to our plugins and applications. Basically, if we are able to change the plugin or application to work with V5 on our test system then the additional downtime to the live site when we upgrade it is minimal... When we do the upgrade from V4 to V5 we have to accept an amount of downtime for the upgrade, but the additional downtime of re-installing an updated application is only a minute or two (typically).
    
2. Changes which require us to redesign pages during the upgrade... Of course, we can test the redesign changes that are required and can test them on the test system so that we know what we have to do during the upgrade of the live system. But, when we end up with a long list of pages and other changes that we must make manually after doing the upgrade then it takes a long time so we effectively have a much longer down period.

Because the V5 pagebuilderupload widget does not work correctly that leaves us with two issues when it comes to upgrading our live system to V5:

1. You are pushing us into extended downtime during the upgrade because we have to manually go into each page and modify it. (I'm not even sure what the solution would be at this time, but whatever the solution it is going to take time to make manual changes to the widgets, layout, whatever...)
    
2. The feeds that you told the <someone else> about do not do what we want... (Of course, they are very nice when you want what they do!) Among other things, the feeds display additional information that we do not want to have displayed. For security reasons we do not want the author name or other details displayed and there may well be other information that we do not want in the display.

Thanks,

John

3 minutes ago, BN_IT_Support said:

Marc,

Thanks for your reply, but I believe that you are wrong...

Your response to someone else was with reference to "feeds" and they work differently. As your response to the someone else said, you can configure feeds in many different ways. The issue is that the pagebuilderupload widget does not work correctly and is not properly configurable in the way that you describe for feeds.

Of course, I get it that V5 is different. Let's consider two types of changes and the IMPACT ON DOWN TIME when I upgrade a live website...

1. Changes which require code changes to our plugins and applications. Basically, if we are able to change the plugin or application to work with V5 on our test system then the additional downtime to the live site when we upgrade it is minimal... When we do the upgrade from V4 to V5 we have to accept an amount of downtime for the upgrade, but the additional downtime of re-installing an updated application is only a minute or two (typically).
    
2. Changes which require us to redesign pages during the upgrade... Of course, we can test the redesign changes that are required and can test them on the test system so that we know what we have to do during the upgrade of the live system. But, when we end up with a long list of pages and other changes that we must make manually after doing the upgrade then it takes a long time so we effectively have a much longer down period.

Because the V5 pagebuilderupload widget does not work correctly that leaves us with two issues when it comes to upgrading our live system to V5:

1. You are pushing us into extended downtime during the upgrade because we have to manually go into each page and modify it. (I'm not even sure what the solution would be at this time, but whatever the solution it is going to take time to make manual changes to the widgets, layout, whatever...)
    
2. The feeds that you told the <someone else> about do not do what we want... (Of course, they are very nice when you want what they do!) Among other things, the feeds display additional information that we do not want to have displayed. For security reasons we do not want the author name or other details displayed and there may well be other information that we do not want in the display.

Thanks,

John

Thats the longest way I have ever seen of saying "Im not seeing those options" 🙂 Added a bug report for that, thank you 🙂