Myr

I'm sorry for leaving you hanging without a more specific reply.
If you're upgrading from 4.4.x the current release will work for you without any issues. If you're looking to install the application on 4.5, then you'll need to wait for the next update. The biggest change with the 4.5 release is how data is stored since it no longer meets the Marketplace guidelines (which is why I haven't yet been able to mark it as 4.5 compatible).
An official '4.5' version is still coming though.
As usual, if you have any issues you're still more than welcome to submit a support ticket on my site for assistance.

Can we get the Page Builder: Text Widget with the rich text editor or can we get the WYSIWYG Widget with the advanced settings of the Page Builder: Text?

 
It feels awfully odd to get a text box where you can't edit anything about the text and call it a Page Builder: Text.  What is the use case for that?

@stoo2000, any updates?

@stoo2000 Is this getting updated to invision 4.5?

This is the only thing left stopping me from upgrading...  Hopefully he releases it soon.

This is the only thing left stopping me from upgrading...  Hopefully he releases it soon.

This is the only thing left stopping me from upgrading...  Hopefully he releases it soon.

Can we get the Page Builder: Text Widget with the rich text editor or can we get the WYSIWYG Widget with the advanced settings of the Page Builder: Text?

 
It feels awfully odd to get a text box where you can't edit anything about the text and call it a Page Builder: Text.  What is the use case for that?

Can we get the Page Builder: Text Widget with the rich text editor or can we get the WYSIWYG Widget with the advanced settings of the Page Builder: Text?

 
It feels awfully odd to get a text box where you can't edit anything about the text and call it a Page Builder: Text.  What is the use case for that?

Can we get the Page Builder: Text Widget with the rich text editor or can we get the WYSIWYG Widget with the advanced settings of the Page Builder: Text?

 
It feels awfully odd to get a text box where you can't edit anything about the text and call it a Page Builder: Text.  What is the use case for that?

Okay 🙂
any chance of getting a more versatile option for those of us that desire them? 
And yes, I know I can fuss around with code, but that's time consuming for those of us that don't do it day in and day out. 🙂

Can we get the Page Builder: Text Widget with the rich text editor or can we get the WYSIWYG Widget with the advanced settings of the Page Builder: Text?

 
It feels awfully odd to get a text box where you can't edit anything about the text and call it a Page Builder: Text.  What is the use case for that?

Can we get the Page Builder: Text Widget with the rich text editor or can we get the WYSIWYG Widget with the advanced settings of the Page Builder: Text?

 
It feels awfully odd to get a text box where you can't edit anything about the text and call it a Page Builder: Text.  What is the use case for that?

Thanks. Having some capabilities on the front-end would make it more consistent with the rest of the software. 

Will it be possible to get color settings in the theme for the Section title/Categories?

If they are currently, there, they aren't blatantly obvious.
Thanks
 

@Charles Any chance of getting MailChimp API integration built in for people interested in paying for the service?  We already use it for our Newsletter and being able to do transnational, and especially follow up emails for purchases, would be very handy.

Cool.
I know the tool isn't flawless, but it is what Google offers and we all must dance to Google's tune or pay the price in the rankings.

@stoo2000 I also thank you for the help you provided.  Our site is running great with this app. I also highly recommend it!

@stoo2000 I also thank you for the help you provided.  Our site is running great with this app. I also highly recommend it!

@stoo2000 I also thank you for the help you provided.  Our site is running great with this app. I also highly recommend it!

If you click on an actual blog it will format the stats (entries/comments/views) correctly with {number="$variable"} but when listing all the site's blogs the template doesn't format the number and just outputs it {$blog->num_views}.  We have blogs that have well over a million views and it looks ugly not being formatted correctly.  Obviously I've changed our template, but I think this should be corrected at the template level for everyone using blogs.

Eh.  How about in 4.3?
Our site has an age range from 14 to 86 and according to Google, we're oddly even across all age groups.  We want to cover ourselves and protect our members so we need to have a functioning birthday system. Right now it appears that these systems don't tie together very well as far as setting a birthday goes: COPPA/Registration/Profile Completion/GDPR requirements.
In 4.2.6, You cannot use COPPA and Profile Completion at the same time.  This is just plain silly.  If COPPA is on, trigger an extra dialog.  Force filling out the birthday field.
In 4.2.6, if you have COPPA off and you set "Birthday" as a required field in profile completion, it only requires the year.  It accepts the current year and ignores month and day.  I'm pretty sure infants aren't posting on the forums, so that's ridiculous.  Between COPPA and GDPR, website operators would be in some trouble collecting data if you are under 13 or 16.  This should be addressed somehow.  Setting a minimum age requirement?  requiring month,day and year to be filled out.
In 4.2.6, the system allows you to edit the birthday when you edit the profile and does no checks at all on it.  (Though if you profile completion on and they change birthday year to not telling, it does trigger profile completion again)
Can we also get a built in user setting to let the member display their birthday or age or both on the Calendar?  Given GDPR, just displaying birthdays on the calendar without getting permission seems like it violates the law.  We've manually added a custom field to do this, but I'd rather have it built in so we don't have to maintain modifications and plugins.

When moving a topic, the Clubs option is quite all over the place. Especially if you have a lot of forums inside a Club. It would be better if they were better organised. Just like the forums tab.

This is where PWA (progressive web apps) enter the game.
Minimum common requirement: Automatic "installation" of a Desktop icon + Push notifications tied to regular IPS notifications and a bonus feature like in the "custom notifications" marketplace plugin. That's what most of us pray for. Shows communities in a browser, hence all IPS functionality is preserved during online access times. We can have everything without restrictions. For offline access: Let us define areas like IP.Pages articles with more or less static contents. This way users can browse those contents offline and it feels like a real app Unfortunately we can't conquer the app stores, but this is neglectable. That's it and probably the easiest way. It accomplishes the basic requirements, the framework is economical and affordable, and an implementation in communities doesn't require a lot tech-know-how
Totally agreed, that would be a game changer. I love this vision! 

We have several blind or near blind members on our site using screen readers and we've been asked if we could request cover photos have an alt description added to them.