WP V0RT3X

Why? F'me if i'm wrong but there is a clear warning in front of the upgrade which you have to acknowledge with a slider!
But well I can feel the pain of @Davyc and others but if you're running a big site then why the heck don't you have a test environment? It takes a few minutes to migrate to a playground and test the upgrade and plugins there!
I made the upgrade in test a few minutes ago and i know that we can#t upgrade yet! 2 Themes and 3 Plugins get blocked, now i can wait for the devs in piece and silence 😉
 
Chris
 

I've been experimenting with the Gallery app, considering a purchase in order to enhance my current Core + Pages installation.
Please implement the following QOL improvements, and I'd be very happy to pay for the app:
 
Shared Galleries for Post Editor
Allow the ability to use images uploaded to a Gallery Album (or category of albums), set at the Usergroup level. As it currently stands, only the user that directly uploaded an image to an album can later access the same image when creating a post/CMS Page/similar.
The user who originally uploaded images to an album called "Shared Art" can then go to a CMS Page/Article, click edit, then head to 'Insert Existing Attachment' and see this:
Admin (original uploader of Gallery images) view:

However, another user (let's call them 'TestUser') who is in a Staff/Moderator group, who I might want to be able to also edit CMS Pages and insert the same images, currently cannot do this:
AnotherUser (moderator usergroup user who should also have access) view:

Please add a new permission, something like this:

This way, a user in the group can access images uploaded to that album (or category of albums) as if they uploaded it themselves.
If the "Insert Existing Attachment" location is not a logical place to set such a feature (because you would only expect user-uploaded images to exist in this menu), then please create a new option that does make this logical.
 
Post Editor Dropdown Menu for Galleries
In addition to the above idea, it would be great to enhance the discoverability/filtering of images within the Existing Attachment menu in post editor too. Please see the below concept; a simple dropdown box can help filter and sort images and allow users to quickly fetch the item they need. This will be useful for the above 'Shared Gallery' feature as well as solo Gallery users who just need an extra method of filtering the non-shared images they uploaded on their account.

 
Hooks for CMS/Pages, Custom Fields & Album Tagging
I want to tie certain Galleries into specific records in the CMS/Pages app. There appears to be no simple way to do this - there's no ability to set custom fields for galleries (thus creating a unique ID/hook in order to tie a Gallery to a Record ala Database Relationship/Reciprocal Items method). There doesn't even seem to be a way to set Tags or Prefix Tags to Albums (only on images themselves - unless I am missing something). The opportunities for coders to extend the capabilities of Gallery in the same way they can Pages seems extremely limited, and it would be great to allow closer integration with CMS using various custom field calls and cross-linking relationships with Page Databases.
 
Smaller QOL Improvements
Things like being able to rename uploaded items (it's every admin's nightmare having to see image13362363556.png on their server...), crop an uploaded image via the Image Tools features, and perhaps create custom Record Images for CMS/Pages from images in Gallery (as a cropped copy so as not to modify the original uploaded image) would be lovely as well, if they could be looked into (unless they exist already and I haven't seen them during my demo test with the app).
 
If these were considered, acknowledged and implemented you'd get a sale from me, for sure. 🙂 

You have almost no control over the appearance of the topic created via Page. Even as an admin, there is no edit option. E. g. you cannot remove the backlink, even if there are no permissions for the database. The template above will only be considered while you make a new record. If you change the template and try to rebuild the topics afterward, all your customization will go.
 

It just moved here.

Savior is here! 🤫

We can only skip the news, if it is indicated to whom it applies. 
Scenario A:
“Streaming is coming (to enterprise plans)” I am not not on that plan, so moving on. Otherwise it will be scenario B:
“Streaming is coming!” Getting exiting. Having to research the details. Finding out to whom it applies. Being frustrated.  So, it’s very much about how the news are presented. 

Seriously, what is the point of announcign this feature on this public community when it will be only available to " corporate and enterprise" cloud plan ? How many clients does IPS have on this plan ? what %age of this community members does this represent ?
Announcing features only available to a few % of your clients can only frustrate the vast majority.

If you "Upgrade to Cloud" in the Creator plan, you are going to lose a lot of functionality, that is included in self-hosted. E. g.
no Pages databases no custom apps except those placed in Marketplace no API access (e.g. webhooks or REST API) no integrations like SendGrid, Pixabay, Facebook Pixel, Maxmind etc. no Elasticsearch and thus no similar content widget based on it no hosting in the EU This is what I understand from the new pricing plans. So, it is indeed a feature downgrade, if you switch from self-hosted to Creator. You have to go with Creator Pro to get the same functionality you have as self-hosted.

There could be an option though in the widget itself. Apply ipsBox? Yes/No. This would not break anything and anyone can set it the way they needed. 😉 

The higher prices will have a big impact on the Marketplace too.
- Many ppl will leave IPS -> less sales in the MP.
- The ones that don't leave won't invest as much as before in addons.
- Less addon sales will make devs switch to other platforms.
- Less and bad supported addons will frighten new customers
(that and the high prices for the basic backage of course).

Disappointed that the store was not built with Commerce....
Why do you guys not use your own products? Support with Commerce is ceased, now brand shop with Shopify. What next? Moving community blog to WordPress? Gallery to Instagram? Clubs to Facebook groups and Calendar to Google? Then "just" connect everything with Zapier. 

In ips.ui.infiniteScroll.js you have this method:
_getPageURL = function (pageNo) { return elem.attr('data-ipsInfScroll-url') + '&' + options.pageParam + '=' + parseInt( pageNo ); }, This does not respect friendly URL. The UI widget attempts to load:
https://example.com/articles/&page=2 (Error 404)
It should be:
https://example.com/articles/page/2/

Yes, that works. It's also a fair bit to type, so in my site I have it in a shorter form:
{{if member.language()->id === 1 }} English {{else}} Esperanto {{endif}} en_US in my site has the id 1. You'll have to adjust your code as necessary.

Sounds good, but if customers leave and addon sales drop, free licenses won't keep devs here.

The higher prices will have a big impact on the Marketplace too.
- Many ppl will leave IPS -> less sales in the MP.
- The ones that don't leave won't invest as much as before in addons.
- Less addon sales will make devs switch to other platforms.
- Less and bad supported addons will frighten new customers
(that and the high prices for the basic backage of course).

The frontpage with the tabs was a little tricky and we use some custom stuff a regular visitor doesn't notice on first sight too, but with such a great tool like Pages almost everything is possible 👍

 

You can do that with custom fields in the app. I can post a screenshot when I'm back home. 
[edit] Ok, actually, you don't even need a custom field at all. You type in the name of the movie and the API fetches all infos from an external database. The movie description will be placed in an editor field. In that field you can put your YouTube link or even use html...

In this example I use some extra fields because because the stream itself and some more stuff are for a special usergroup only. It then looks something like this ...

Somewhere here is explained why IPS doesn't come with a dark mode out of the box.
What you can do is installing an alternative dark theme and a plugin that allows users to quickly switch between the themes.
 

What you are looking for is called "Zebra". With the search function of this site you should find some topics how to create that effect.

Hi, I liked the idea and had some spare time so this is a very simple plugin (no settings etc.) to remove that line ...

Hope you like 
Hide Redirect Counter 1.0.0.xml

Another downfall..... 😔

@Mark H, it means there is no way for IPS Cloud customers to test any functionality for guests. Right? Putting the community offline, means there is no access of guests. Testing functionality for guests works only in live production. Like open-heart surgery. 😨
 
 

You would need to purchase a self-hosted license in order to have access to the software files.

I have the same problem when I try to clone download categories 
UnderflowException: (0) #0 /usr/local/apache/hosting/mysite/www/system/Node/Model.php(3051): IPS\Db\_Select->first() #1 /usr/local/apache/hosting/mysite/www/init.php(902) : eval()'d code(225): IPS\Node\_Model->__clone() #2 /usr/local/apache/hosting/mysite/www/applications/downloads/sources/Category/Category.php(758): IPS\Node\radtags_hook_C_NodeModel->__clone() #3 /usr/local/apache/hosting/mysite/www/system/Node/Controller.php(907): IPS\downloads\_Category->__clone() #4 /usr/local/apache/hosting/mysite/www/system/Dispatcher/Controller.php(90): IPS\Node\_Controller->copy() #5 /usr/local/apache/hosting/mysite/www/system/Node/Controller.php(69): IPS\Dispatcher\_Controller->execute() #6 /usr/local/apache/hosting/mysite/www/applications/downloads/modules/admin/downloads/categories.php(44): IPS\Node\_Controller->execute() #7 /usr/local/apache/hosting/mysite/www/system/Dispatcher/Dispatcher.php(153): IPS\downloads\modules\admin\downloads\_categories->execute() #8 /usr/local/apache/hosting/mysite/www/admin/index.php(13): IPS\_Dispatcher->run() #9 {main}