Patreon Lukazuki

There is already the BULK_MAILS_PER_CYCLE constant to solve issues with hosts that have trouble with many emails at once. 
Equally, if not more important, is how many emails are sent in a given timeframe. It’s normal for hosts and email services to have some kind of limit in that regard, but with the way IPS sends out bulk mail, it unpredictable when these limits are being hit and there is no way around this problem when the limits are hit. 
I suggest a solution like a MAX_MAIL_CYCLES_PER_TASK constant or setting to limit the amount of cycles run each time a cron is being fired. So, for example, I could set 1 run of 100 emails with the cron running every minute resulting in 1000 mails in 10 minutes. 
I understand that IPS isn’t all that focussed on features that would only help self-hosted customers, but it seems like an easy implementation which could help a lot of users. It’s actually the behaviour that people are already expecting. 

So, to me, this is absolutely bonkers. 

IPS' team has noticed that their plugin community is a fraction of what it used to be, thinks this is because everyone has switched to bespoke work (You sure it's not the other way around? People using bespoke work /because/ the plugin community has a fraction of the size it did back when there was a free version and before IPS was trying to be everything for every person by default?). 

So they /murder/ pre-made plugins. No, we're not going to see thriving new marketplaces. Excited devs will start some, none of these will be as active as the current one, most if not all of these efforts will peter out quickly. Not having the marketplace in the panel, not having them vetted by IPS, not having people browse over them prior to purchasing IPS (and plan out a setup with plugins), not having their plugins listed on IPS' websites are all small cuts that together, cut deep. IPS' website was never a limiter on other marketplaces (they've always existed for themes and some plugins), but free advertisement to those who did have those. You're merely taking away an option and your stamp of approval. 

And you do this brilliant move in the middle of a version, announcing it to your costumers roughly a month up-front. 

Definitely not obvious you're springing it this way to ensure customers don't either, mass-hug a former major version to keep their plugins, or start planning migrations away from IPS between the time of announcement and release. 

Now, months after it happened, I google 'Invisionpower plugins marketplace' and find nothing on the first page. 

Sincerely, as someone who was a fan once of IPS, you people suck.

Subscriptions have been available for some time now and offer a good way to monetize your community. It would be nice if each subscription had the option of multiple offers - time frame/settings. Most sites these days offer a discount for an annual subscription. In IPS, you have to create an entirely new subscription/box rather than something like:

 

Anyone at invision explain the thinking behind these two sets of statements...
 
Commerce Deprecation
Commerce Help Feature - Now, there are many email support desk solutions that are a significant improvement on what Commerce offers...
...we made the decision to deprecate the support desk feature
Commerce Sales Feature -  ...physical product sales have now been deprecated and are much better handled by specialist services such as Shopify.
versus
New Courses and Lessons Feature
The Courses app is not going to try to be a full LMS. Not trying to run a university here 🙂
 
As I see it invision are...
Getting rid of 2 features (that I use heavily) with the reason being you can get better commercial versions elsewhere
Whilst adding one new feature (that I have no use for) even though you can get better commercial versions elsewhere
All a bit conflicting to me
Plus while here, may as well ask, will the cost of commerce go down now as it will be a lesser product for self hosted packages?
 
 
 

Hi,
I have a category of Downloads which is just a category with several sub-categories containing various files. The sidebar widget shows them correctly, but when I navigate to the parent category, it says "No files in this category yet."

 
I noticed it does this here in the Marketplace for example in Themes, but not on my own site?
Many thanks!

I’m not judging in any way, just listing some observations about the developer/Marketplace situation in the recent years. 
4.5 tightened the rules drastically. Result: several developers left for good. price increases. Developments needs a self-hosted installation and possibly a demo website. It’s now 850 + 300 annually. Someone starting out as developer really needs some killer products to earn that back and then generate profits. Cloud testing of resources would make it even more expensive (+1,788 annually).  Shift/changes to cloud. The lower tiers don’t have the ability to install third-party products. This decreases the reach and makes running independent third-party shops less useful/profitable.  Signatures turned off. No possibility for passive advertisement through community posts.  Limited compatibility field. Sales can only be created for one version, limiting the income.  I have no magical solutions to offer, but are improvements for this something we could put on the table for 2023?
Currently, I am not very optimistic. We only have a handful of active developers left with continued announcements of departures. If it is still working well for some (?), it’s probably because of a large set of files and existing customers with renewals. But I can’t see how new developers would want to get involved in the current situation, replacing the ones who left or even growing the marketplace. 
I understand the costs and downsides for IPS. Paying for code reviews, chargeback fees and of course all the support issues with third-party resources. But then again: Looking at the broader field of online software: all the big players strive with and in part because of a flourishing third-party marketplace. So, improvement could easily be a “win-win-win” situation for IPS, developers and IPS customers. 
 
(I would have some suggestions myself but I don’t want to push the topic in a specific direction, so I am leaving it at the problem statement for now.)

Not necessary. I can speak for myself.
You do not respect the terms of my support, which you have to agree when purchasing, etc.

 
First: sent a message reporting an issue with Rest API in a resource. It was fixed as pointed in the release note of the version. Released. I appreciate the report, although you didn’t do it as requested in the item 4.
Second: you asked how you could do something code base related. Item 2 of my terms makes clear the scope of my support. I’m not here to teach you how to make things. If you’re not happy with it, just don’t renew the purchase.
You were blocked for this one, not for the support request, which although made in a wrong way, was attended and the issue fixed.
Thank you.

Hi @Runar could you consider extend the Marker functionality for the post too?
Example, a topic with so many posts with different contributions, I would like mark posts so that markes will be able to shown you which post contains information of a specific question or content. People with that markes avoiding reading post by post to find useful information, for later user avoiding asking repeatedly the same question and repeatedly giving again the same reply.  

The user's nickname is not completely centered on the avatar. Just remove the unnecessary left margin.
@Ehren
html[dir="ltr"] .ipsComment_author > *:not(:first-child) { margin-left: var(--sp-2); flex: 0 0 auto; }

4.5 introduces some changes to CSS, so I wanted to provide an overview of those and how they might affect you.
 
IE11
Firstly, we've completely dropped support for IE11. This means you'll start to see newer CSS methods being used that IE11 does not support. 
 
Atomic classnames
One thing you'll notice as you read on is we're moving towards using atomic classnames for utility styles. What does that mean? Basically, each classname is just a convenience helper for applying one particular style. You build how an element looks and behaves by applying multiple classnames. 
While this is slightly more verbose in the HTML, it's also much clearer and avoids having to create mutant selectors that exclude certain elements. If you see an element with ipsBorder_top, it's obvious what it does. Don't want a top border? Just remove that class.
Another benefit is that it allows more precise control over how styles are applied at different device sizes, because individual styles can be modified. Want a top border on desktop, but not phones? ipsBorder_top sm:ipsBorder:none will do the job - no crazy selectors or additional media queries necessary.
 
Class prefixes/modifiers
Wait, what's that sm: bit in the atomic classname example above? That's a new naming convention you'll see which controls at which breakpoints the style is applied.
Unprefixed (e.g. ipsBorder_top). Applies to all devices, desktop and smaller. md: (e.g. md:ipsBorder_top). Applies to tablets and smaller. sm: (e.g. sm:ipsBorder_top). Applies to phones only. sm and md prefixes take priority over the desktop classname. This means you provide the desktop classname but can override it for tablets and/or phones by also adding an md: or sm: classname. For example, ipsPadding_top:double sm:ipsPadding_top:half applies double top padding on desktop, but only half top padding on phones.
You'll also see modifiers on some classes (as in the example above), for example ipsPadding:half. ipsPadding is saying 'apply padding to all sides', and the ':half' modifier makes it a smaller amount.
 
BEM classnames for modules
While we're using atomic classes for global utility styles, we're moving towards BEM for module-specific classes. BEM is simply a naming convention, so it doesn't have too much impact on you - you'll just see a new structure for new classnames that should be easier to understand. 
 
Note: We haven't rewritten our CSS framework with the atomic classname, class prefix/modifier or BEM approaches. Don't worry - 90% of the classes you're used to will be the same. I just wanted to point out that going forward, new classes will follow these paradigms.
 
CSS Variables & calc
We're now making use of CSS variables (also known as CSS custom properties). Check out this MDN article if you aren't familiar with them. This enables us to define some values in one place but use them throughout the product - and it allows you to change the value in one place if you wish to do so for your theme. Most of our CSS variables are defined at the top of global.css in the CSS framework, but you'll also see some other local variables defined in other places. Variables are simply used by wrapping the name in the var() function, e.g. var(--positive-light). 
You'll see some variables named --sp-1 and so on. This is our new 4px spacing scale. In 4.5 and going forward, when we style elements we'll generally be using one of these values for widths, heights, borders, spacing etc. to keep everything consistent. You should do the same for elements you create.
We're also making use of calc(). This is another CSS function that allows math operations to be done. Instead of having to hardcode numbers for positions, sizes etc., we can now use calc() to do it for us based on some other values (often CSS variables).
CSS Variables for theme settings
We are deprecating the usage of the {theme} and {hextorgb} tags for color-type theme setting keys (but not for non-color settings or when you need to pass a specific hex code in).
Instead, color-type theme settings will automatically have a CSS variable created for them, named --theme-setting_key, where setting_key is the key of the setting as defined in the AdminCP. The variable will be a triplet representing the color, for example 255, 255, 255. Therefore, this value can be used with both the rgb and rgba CSS color functions.
Here's an example. If in the past you'd wanted to use the area_background theme setting in your CSS, you'd do background: {theme="area_background"}. Or if you want some opacity, you'd do background: {hextorgb="area_background" opacity="0.2"}.
In 4.5, the correct way of using these will be: background: rgb( var(--theme-area_background) ) and background: rgba( var(--theme-area_background), 0.2 ) respectively.
We're doing this now because it will open up some exciting functionality in future. To be clear, any existing usage of {theme} and {hextorgb} will continue to work fine in 4.5, but we encourage you to move over to the CSS variable approach.
 
Hardcoded hex values
In 4.5 we have largely removed all hardcoded hex colors from our CSS files, and adjusted styles to use theme setting values instead. This will make it much easier for admins to fully colorize their theme without hardcoded colors messing things up. I encourage you to update your app's CSS to follow this approach.
 
Font sizes
We've moved font sizes to a fixed scale. These have been implemented as theme settings so they are customizable. However, rather than use the theme setting value directly, you should make use of the new {fontsize} plugin. This plugin ensures the global scale is applied to any values passed in, allowing 'large print' versions of themes to be easily created. You should use the {fontsize} plugin for font sizes both when you use one of the theme settings and when you use specific pixel values (e.g. {fontsize="72"} - for 72px text)
When used with the {fontsize} plugin, the type scale keys are:
x_small (12px) small (13px) medium (14px) base (16px) large (18px) x_large (20px) 2x_large (24px) 3x_large (30px) 4x_large (36px)  
Flexbox
While we've used flexbox in some places in previous versions, 4.5 makes much wider use of it and also introduces a new family of classes. If you aren't familiar with flexbox, I highly recommend this CSSTricks article for a primer on it. Essentially, instead of positioning elements using floats/clears/etc., flexbox treats the container as a flexible box with properties for controlling how elements inside of it as laid out.
4.5 has a number of new classes that are essentially just convenience for the usual CSS rules.
ipsFlex (sets element to display: flex) ipsFlex-ai:start, ipsFlex-ai:center, ipsFlex-ai:end, ipsFlex-ai:stretch (ai - values for align-items property) ipsFlex-as:start, ipsFlex-as:center, ipsFlex-as:end, ipsFlex-as:stretch (as - values for align-self property) ipsFlex-jc:start, ipsFlex-jc:center, ipsFlex-jc:end, ipsFlex-jc:around, ipsFlex-jc:between (jc - values for justify-content property) ipsFlex-fd:column, ipsFlex-fd:row, ipsFlex-fd:column-reverse, ipsFlex-fd:row-reverse (fd - values for flex-direction property) ipsFlex-fw:wrap, ipsFlex-fw:nowrap, ipsFlex-fw:wrap-reverse (fw - values for flex-wrap property) ipsFlex-flex:10 - sets flex-grow: 1 and flex-shrink: 0 ipsFlex-flex:11 - sets flex-grow: 1 and flex-shrink: 1 ipsFlex-flex:01 - sets flex-grow: 0 and flex-shrink: 1 ipsFlex-flex:00 - sets flex-grow: 0 and flex-shrink: 0  
All of these classes have md and sm prefixed versions too, and this opens up the possibility of having different layouts on different device sizes in a way that's much easier than the hoops you'd have to jump through before. For example, to create some elements that show as a row on desktop but collapse to a column on mobile, you'd just apply ipsFlex ipsFlex-fd:row sm:ipsFlex-fd:column. The sm:ipsFlex-fd:column class overrules the ipsFlex-fd:row class on mobile, adjusting the layout. (Note: flex-direction: row is the CSS default direction anyway, so you can actually leave out ipsFlex-fd:row - it's implicit. I included it in the example for clarity.)
 
Padding/margin
We've added new spacing classes for padding and margin, to allow for atomic classnames, device prefixes and modifiers.
ipsPad, ipsPad_double, ipsPad_half, and all of the ipsSpacer_* classes are now deprecated. You'll still see them in our templates and they'll still work in yours, but don't use them in any new work - you should use the updated classes below.
The padding classes are now named ipsPadding:
ipsPadding, ipsPadding:none, ipsPadding:half, ipsPadding:double - apply padding to all four sides ipsPadding_vertical, ipsPadding_vertical:none, ipsPadding_vertical:half, ipsPadding_vertical:double - apply padding to top and bottom ipsPadding_horizontal, ipsPadding_horizontal:none, ipsPadding_horizontal:half, ipsPadding_horizontal:double - apply padding to left and right ipsPadding_left, ipsPadding_left:none, ipsPadding_left:half, ipsPadding_left:double - apply padding to the left side (RTL aware) ipsPadding_right, ipsPadding_right:none, ipsPadding_right:half, ipsPadding_right:double - apply padding to the right side (RTL aware) ipsPadding_top, ipsPadding_top:none, ipsPadding_top:half, ipsPadding_top:double - apply padding to the top side ipsPadding_bottom, ipsPadding_bottom:none, ipsPadding_bottom:half, ipsPadding_bottom:double - apply padding to the bottom side These classes have md and sm prefixed versions too, allowing you to apply different padding depending on the device size.
One side note here: with the old padding classes, padding was simply halved on phones with no opt-out. That's not the case with the new family - if you want half-padding on mobile on an element, you should apply sm:ipsPadding:half in addition to the normal ipsPadding class, for example. This gives you much more control than you previously had.
Margins follow basically an identical pattern to padding, with the same variation of classes, except the name is ipsMargin.
 
Gaps
Another new family of classes is ipsGap. These classes are used when you want spacing between elements. In the past, you'd have to use :last-child or :first-child to exclude an element, or loop over the elements in the template to leave off a class. If elements wrapped to a new line, putting spacing between the lines was tricky too.
ipsGap solves this by applying even spacing between elements, then applying a negative margin on the whole container to bring it back to the starting position.
The classname is followed by a modifier, which is a number from our spacing scale, e.g. 1 is 4px spacing, 2 is 8px spacing and so on.
ipsGap:1 (1-5 available) - applies both horizontal and vertical spacing around each element in the container ipsGap_row:1 (1-5 available, as well as 0 to remove) - applies vertical spacing on each element in the container Notice ipsGap_row also supports the :0 modifier. This allows you to have horizontal-only spacing - simply apply ipsGap:1 ipsGap_row:0.
Be aware that using both ipsMargin (or custom styles that apply a margin) and ipsGap on the same element can cause issues. You may want add a wrapper element to handle your margin in this situation.
 
Borders
We've also added a class family to add light grey 1px borders to elements - used commonly as dividers between some parts of the page.
ipsBorder - apply border to all sides ipsBorder:none - remove border from all sides ipsBorder_vertical - apply border to top and bottom ipsBorder_horizontal - apply border to left and right ipsBorder_top, ipsBorder_bottom, ipsBorder_left, ipsBorder_right - apply border to a particular side These classes have md and sm prefixed versions too, to control borders shown on each device size. This is particularly useful if you apply a border to a flex child which is in a row on desktop but a column on desktop, for example - you will be able to easily control which side the border appears on once collapsed.
 
"Pull" class
To better display content areas on mobile, a class named ipsResponsive_pull has been added which 'pulls' a box on the left and right sides on small devices. It's intended to be used on boxes (normally with the ipsBox class) that you want to take up the whole screen width on mobile, allowing better usage of the available screen space.
 
Template changes
We've worked to keep template changes as minimal as possible, but in an update the size of 4.5 there are still quite a number of changes. Whether these impact you will depend on if you've modified the template (for theme designers) or rely on a particular selector for theme hooks (for developers).
One area that has received fairly big changes is the post/comment templates. We have redesigned the headers and footers of these templates and moved some elements into a separate parent element on mobile devices.
As usual, full template changes will be available once we've released betas.

overall not bad, compared to what was on the previous ips versions, actually, there is an improvement, only this mobile version lags behind a lot 🤐

very good point, I was also wondering about it how to fix this 🙄
there is no such option in the setting to set a downloads link in (target="_blank")
all downloaded files are open in the same window 🤐

for example, as I want to upload a free file to the market, I have the license but I need to pay a 40usd to upload a free file, seriously? 😂 the policy followed by IPS is absurd and anti-development.

When we create a topic, the URL is created from the title of the topic. In the case of a long topic title name, it would be useful to have the option to manually change the URL, as it is for example in WordPress.

Why?  According to Backlinko, "Shorter URLs tend to rank better than long URLs." To prove this, they performed some extensive testing on one million Google search results.
Here’s a graph that shows how Google rankings decline as URL length gets longer.

It’s pretty cut and dry. Notice how the number one position has URLs with roughly 50 characters.
But once you move down to the number 10 spot, the average URL has 62 characters.
So somewhere around 50 – 60 characters is a pretty good number to shoot for.
If you go way beyond (say 80+ characters), this is likely to have a negative impact on your ranking.

for example, as I want to upload a free file to the market, I have the license but I need to pay a 40usd to upload a free file, seriously? 😂 the policy followed by IPS is absurd and anti-development.

I see, but I don't see how an active license will serve Marketplace authors. It serves IPS more than Marketplace authors. 
I am aware of this, but you guys should consider the free sources your clients are using from Marketplace. You should allow them to install any update if the app or plugin already installed on their communities free or paid. 
Today I have completed 16 years as client with IPS, and you guys treat me like someone just registered his account a new member. My profile says so. 

As I am a client, but my license only expired. Why cannot I access free apps or plugins update whenever my license is expired and only accessing the paid ones? This is completely unfair. 

I caught this bug on chrome, firefox, and opera, I have the latest version 4.6.9 updated a few days ago,
and I checked it on another installation on localhost and this bug can also be done there 🙄

It's seriously a stupid system (pardon the language). There are several plugins that are being left behind now due to Covid, stuck on 4.5 but works just fine on 4.6. But since you can't install them or download them you simply can't use them. I have this very problem now on a fresh install and it's honestly frustrating that the devs decided to lock down the plugins system this way. I'm not a developer and I can only guess that tons of devs also lose revenue on this since it's no longer worth buying or renewing licenses...
I would really like to see a way to install plugins from older versions or at least being able to manually download a plugin I have bought and have a license for, because you are basically disallowing owners of a license to use the product.

overall not bad, compared to what was on the previous ips versions, actually, there is an improvement, only this mobile version lags behind a lot 🤐

you can do that by CSS
/* everywhere hidden */ .someclassName { display:none; } /* visible only on store */ body[data-pageapp="nexus"] .someclassName { display:block; }

you can do that by CSS
/* everywhere hidden */ .someclassName { display:none; } /* visible only on store */ body[data-pageapp="nexus"] .someclassName { display:block; }

here is the button you seek
 

Someone here is fearing to missout on dark theme sales.
This would be a great addition, and has become standard for any great web service these days.
For example right now i'm almost losing my perceptual vision because i'm on this website.

don't worry, already they know about this problem