DesignzShop

@Rikki Sorry, I may be being thick headed on this Rikki, So just to get this straight and see if i got this correct...
We need to convert our custom hex color setting to a rgb or rgba variable like listed above in our custom.css? And to be clear here again so I understand, we are still using a hex color in the custom color setting and not a rgb or rgba, or do we need to convert our custom color setting to a text field and use for default a rgb or rgba color code?
 
 
As an example, let's say I have this rule below
.ipsPromote .ipsPromote_icon {
  color:{theme="mass_color_ffffff"};
  background:{theme="mass_color_main"};
}
Is it supposed to look like this to be correct?
.ipsPromote .ipsPromote_icon {
  color: rgb{ var(--theme-mass_color_ffffff"};
  background:rgb{ var(--theme-mass_color_main"};
}
 
 
Next, if I use a custom text field and use a rgb or rgba in that field like so, is that proper or ok to do like I have it or do I need to convert this too?
.ipsWidget .ipsTabs_small .ipsTabs_item:not( .ipsTabs_activeItem ) {
  color: rgba({theme="mass_color_rgba_0_0_0"},0.80);
  border-top: 7px solid rgba({theme="mass_color_main_rgba"},0.15);
}
Is the code above then supposed to look like this if I use your given example above
.ipsWidget .ipsTabs_small .ipsTabs_item:not( .ipsTabs_activeItem ) {
  color: rgba( var(--theme-mass_color_rgba_0_0_0}, 0.80);
  border-top: 7px solid rgba( var(--theme-mass_color_main_rgba}, 0.15);
}

Not really called for here. No reason to resort to this. You may want to consider using your own advice here.
@Adriano Faria is exactly right here.
Instead of tongue lashing this person, just turn the submission in and let IPB decide if it needs to be available or not.

All I really got to say is IPB knocked this one out of the park. HOMERUN! I better add also I'm also really impressed with low bug count in betas. The dev team is organized better than ever.. It's taken some years to get everything on the track it is but I feel it was well worth it and well worth the wait. Should I be giving @Lindy some credit here?? If I do will @Matt pull the Lindy factor line on me? 🤣 This is really such a well rounded product now all the way around. Great awesome job IPB!
 

It's all good Rikki imo... Some people will be late to their own funeral..

Thanks for the responses.  IPS Techs got it resolved. We needed to unblock an ip.

Thing is you can take out ranks and pips and with my theme adjust the size of the profile picture and width of profile area. The reference I was making is you can make the width of the profile area to go into the text area to make it smaller. 
I also wouldn't say people are stupid either. In todays world like I said it's all about me, me, me. If that's what people want, I give it to them, if it's not what they want, I make it adjustable 🙂 
Also as I said above, most of the people who use my themes like it like you see it. Whether they post a word, 5 lines or 20, it's about them. 
If you looked also you'd notice the only thing that's been enlarged in that screenshot is the profile picture. Everything else has stock IPB css as far as spacing goes. I just wrap around it. Pretty simple, you don't want a large post profile photo, adjust it. But I can guarantee most people want the full size post profile photo instead of something they can barely see.
I've also never had a complaint about that area or the adjustability of it, most end users don't live in 1990 with everything smashed together.

I did the same thing. People like to show off, they want their data out there (especially in the case of my site which is a site for other sites to list at). I have badges for people to show off their nerdy pride (like which type of Bender they are, which GoT House they are, which Hogwarts house they are a part of etc).
I'm working on my 4.5 version of my site and I am likely moving this away from being a sidebar into being a header of author information instead.
But as @DesignzShop said it really depends on the community.

Your personal preference may be getting in the way of what your community really thinks. As an example I redone my themes post profiles and even made them larger in accordance to where they were. One of the biggest compliments and most feedback I've gotten is how the post profiles stand out.
Most users now days are all about the me, me, me thing. Take social media for example. Facebook, Twitter etc... are all about highlighting one person as a general rule. I'm not referring to businesses here, just an individual account. They want to be seen, they want to have their posts, tweets, counts, likes, etc.. out there for everyone to see. Again, it's all about me, me, me.. 
From my past feedback, users wanted full post profile pictures, highlighted post counts, wider post profile to take up more blank space in the post. By making the profile wider I removed some of the posting area and made each post more about the user than ever before. This may not be for everyone, but like I said, it's been a pretty big hit from the feedback I've gotten.
Of course not every individual may not like one approach but in general, but what I've done has far outweighed the no compliments to a bland, stripped down user post profile.
Another issue I've seen also in the past is admins / people who are more code conscious tend to want things stripped down. Most end users however want to see more, especially if it's about them.

Can you please consider adding space after a second line of tags start in mobile. I add quite a few tags to my articles and when the line drops there's not enough space between the first and second line and they sit on top of each other.
Regards

We were in beta for months, alpha for about a month before that. We've been talking about 4.5 since last year, and announced the new front end theme in April. We've been running a beta version on our own community here for months.

I understand your point that you can't be expected to obsessively follow every bit of news we release, but with a major upgrade you should take a short time to investigate the changes before pressing the button.

I appreciate the feedback but I think it's a little unfair to state that you didn't know what was coming and now regret it.
We also have to design for a wide variety of screen sizes, so the layout has to be consistent and modular.

It's easy to see a lot of whitespace on a single screen with a short topic title and few logged in actions at full screen on a 24" monitor, but when you consider this:


I don't feel that there's much space to save here without cramming it into two lines and accepting some buttons will overflow.

Rikki just answered you and dealt with it extremely well by answering your question and did listen and explained why. One reason I've been with IPB for this many years is because of their open design instead of bunching everything too close. this isn't the 1990's. 
Just because you don't like something doesn't mean it needs fixed. Obviously by Rikkis answer it's WAI.
 
Yes we do, and I think it's just fine and so do many many others.
Have a nice day

Rikki just answered you and dealt with it extremely well by answering your question and did listen and explained why. One reason I've been with IPB for this many years is because of their open design instead of bunching everything too close. this isn't the 1990's. 
Just because you don't like something doesn't mean it needs fixed. Obviously by Rikkis answer it's WAI.
 
Yes we do, and I think it's just fine and so do many many others.
Have a nice day

Rikki just answered you and dealt with it extremely well by answering your question and did listen and explained why. One reason I've been with IPB for this many years is because of their open design instead of bunching everything too close. this isn't the 1990's. 
Just because you don't like something doesn't mean it needs fixed. Obviously by Rikkis answer it's WAI.
 
Yes we do, and I think it's just fine and so do many many others.
Have a nice day

Rikki just answered you and dealt with it extremely well by answering your question and did listen and explained why. One reason I've been with IPB for this many years is because of their open design instead of bunching everything too close. this isn't the 1990's. 
Just because you don't like something doesn't mean it needs fixed. Obviously by Rikkis answer it's WAI.
 
Yes we do, and I think it's just fine and so do many many others.
Have a nice day

Rikki just answered you and dealt with it extremely well by answering your question and did listen and explained why. One reason I've been with IPB for this many years is because of their open design instead of bunching everything too close. this isn't the 1990's. 
Just because you don't like something doesn't mean it needs fixed. Obviously by Rikkis answer it's WAI.
 
Yes we do, and I think it's just fine and so do many many others.
Have a nice day

Rikki just answered you and dealt with it extremely well by answering your question and did listen and explained why. One reason I've been with IPB for this many years is because of their open design instead of bunching everything too close. this isn't the 1990's. 
Just because you don't like something doesn't mean it needs fixed. Obviously by Rikkis answer it's WAI.
 
Yes we do, and I think it's just fine and so do many many others.
Have a nice day

In 4.5 we've tried to keep headers consistent, so that buttons are where you expect them to be, there's space for additional buttons as each page/app might require, and so that each page/app can extend the data shown in the header without the whole thing breaking down. In 4.4, this was a problem - sure, on perfect example pages, the follow button worked well in the top right. But using a different app where more buttons need to be shown, or even just having a long topic title, suddenly it wasn't so pretty and usable. The new header is designed to be flexible and extensible according to requirements.
It's pretty easy to take one particular page and find criticisms - but remember we are designing a suite where each page might have some shared functionality and some unique functionality. We have to design components that can work well in more than one perfect scenario. 

I don't buy into it. In software systems nothing is fully secure. You take it as it comes. That's been common knowledge since day 1.

@LoPoSt The "free space" that you speak of has stuff that shows up in it. The top box that you indicate is where the description goes when/if you have one for the category/section. The place that you want to move the "how many articles in this category" to is where the pagination shows up when you have more than 1 page of items in them.
@Interferon The box you are indicating to is where the description goes (as I noted in the above paragraph). This is something that you can edit in your own theme if you don't intend to put descriptions on your forums.
It may "seem" like dead space but a lot of that dead space is because you don't have content. The specific things you want changed can be done on the theme level for your site specifically.

Paul, the feedback truly is appreciated. With anything, there are inherent risks. You can buy anything and it can go unsupported, warranty denied, or any number of things you hadn't hoped for. The Marketplace is an inherent risk to IPS as well. Anytime there's a fraudulent purchase, a developer disappears and/or there are chargebacks, IPS bears the burden of such - financially and otherwise. When you are dealing with inexpensive resources at a 10% commission, one $15 chargeback it can take dozens of transactions to recoup the loss from that one previous transaction. The Marketplace, from a financial standpoint, is a loss leader for IPS, but it's something that adds value to the product and enhances the customer experience. So, yes, there are risks - for everyone. We've drastically improved the footprint and presence of the Marketplace for 4.5 and thus increased exposure - which ultimately, will be great for everyone. With that, however, necessitates the need to leverage tighter control of the Marketplace. If you buy an app in the App Store or Play, you don't get the source. If the developer disappears, that's the end of the app. That is the unfortunate reality that we all face virtually everywhere else. 99% of the time, the risk pays off.
I completely understand where you are coming from, Paul. Truly. You are fortunate to have the skills and desire to get your hands dirty. I do, however, have the advantage of knowing our customer base and  very respectfully - you are indeed the exception, not the norm. Most want to point, click and go. I understand the argument that has been raised: "why not have both?" - we effectively do, even if it's not quite what you had in mind. You can manually install resources and if you wish to purchase something in the Marketplace, there is nothing stopping you from contacting the author and asking for files and likewise, nothing preventing the author from providing it to you. The only caveat is it's installed through the unofficial installation side of the framework and thus unsupported. Beyond that, if the author agrees with your assessment that you should have the ability to view and alter their resources, what we've done in 4.5 should have no bearing on you. If you're asking to have it like it was, I'm afraid we have no intention of doing so, to be completely candid. Whether that changes in the future is unknown, but at this juncture, we will continue to improve the infrastructure, processes and work with the authors to create the best experience we possibly can. There will be bumps. There always is - as we speak, there's an app I can't open on my iPhone since an update - it just crashes. I've been doing this long enough to know things happen and I don't expect the developer or Apple to catch everything. Likewise, we can't predict the perfect storm in every circumstance and when we find something, we will all learn from it, do our best to ensure it doesn't happen again and rather than mask issues that bubble up outside of the Marketplace, they will be dealt to ensure other customers don't encounter the same thing.
Invision is moving in the direction that the majority of the Internet has already moved towards. Point. Click. Done. Fewer and fewer people have any interest in the nuts and bolts of things anymore. We used to have our own datacenter space long ago. I remember personally, in our earlier years, getting late night calls because a power supply failed, or one of the Cisco 6509's didn't come back after an update, or a processor failed. I know nothing about latest server hardware and I haven't had to telnet into a power strip in years... do you know why? Because I don't have or want to. 🙂 Our infrastructure is housed entirely within AWS these days. They do what they do, so we can do what we do and while they aren't perfect either... it works. That is what the overwhelming majority of customers want. Of course, if I wanted to get my hands dirty and rack a server, there are still colo providers available. If we wanted to download, hack up and mess with a collaboration and communication tool - we could, but why? That's what Slack does and I don't care what their code looks like, or what the third party developer's code looks like. It's point. Click. Done. If there's no done, they will work until there is. Again, it may not be your ideal outcome and I really do understand the mistrust, but we just can't be something to everyone and in this case, we're focusing on the things you shouldn't -have- to focus on vs carving out space for you to rack your own server. Others do that well, but we are moving away from that model and I do realize it's a big change for some. We hate to alienate or turn away anyone, we really do.
In short: I would encourage you to contact authors moving forward if you want a copy of a resource and see if that's an option, either as a courtesy or by purchasing from their site instead of the Marketplace. We are standing firm on our position with regards to how the Marketplace will function moving forward. You have my word and commitment to making that the best possible experience it can be. We will also improve communication for these types of things in the future. I think we just assumed everyone would welcome the change - who doesn't like simplicity, right? There's obviously a few that do care and we'll be more mindful of that.
Thanks again for taking the time to provide concise and constructive feedback, Paul. It's appreciated.

That's a bad analogy right there...  😁
 

That's a bad analogy right there...  😁
 

I don't buy into it. In software systems nothing is fully secure. You take it as it comes. That's been common knowledge since day 1.

In your first paragraph,, I would of contacted support over that since the item was listed in marketplace. I'm also sure if Lindy knew about someone pulling something like that they'd have a issue. I'm positive someone would've looked into that for you.
Your renewals go for more than 3rd party app upgrades, security updates, IPB services, software features and more.
I don't have to pretend on anything. 4.5 is bringing a whole new way of working marketplace. Mlst the people I see selling it now have been here a while and sold a few things. I'm not sure however on IPB's policy on new devs. That's something you'd have to speak @Lindy with. I do know Danial and Stuart are pouring over apps, code, databases etc... before anything gets approved. That means you're getting a quality product that works out of the box. Were also as devs now forced to include any changes in the change log so they know what to review on resubmissions. There's more to that submission process also.

I dropped a forum I had for 13 years, I asked IPB to move that license url to another url that also was using a IPB second license. Then I used the 2nd url on a different domain because it was a full suite, they did, no charge,, I have never had a issue with this probably because I don't switch urls often at all. Point is they were great and done this a couple of years back when this policy of a 15.00 charge was in effect. 
Second, I never understood why people want to let their license overlap. I don't think I ever let that happen for myself in all the years I've been here. I always wanted the latest version so I could keep my sites safe with current bug fixes and security updates. My members and my investment meant that much to me.