My Sharona

Matt, you have to understand that most of the customers previously edited the theme by modifying the changes directly in the cores's CSS. Hence such a big disappointment.
We both know that this is not a good practice and this change was needed, but nevertheless put yourself in the role of a customer without much technical knowledge who just wants to modify his theme, as he has done so far and knows this type of editing also from others CMS.
This is a big change and it strongly influences the way the theme is edited. I understand both sides.
In the end, I think it will be good for all of us, both for the customers and for the software itself.

Also make sure the online indicator does not stay on for members who are anonymous. Online indicator must not stay on for anonymous members.

I would be cautious to judge who is the majority and minority based on personal experience. Services like Discord are ubiquitous in SOME circles, but even with their 150 million active users it’s just a tiny slice of the daily internet use of billions. If I would ask the 20 people closest to me, independent of age or background, I bet most wouldn’t even know Discord, let alone use it. And that reverses the argument of “why join a different forum when everyone is already on Discord”. Why even install that strange, unknown app when no one you know uses it? 

My site runs on a dedicated server. I go through a very small company. When I call, they answer the phone and immediately help. PM me if you want details. The amount your spending is crazy. 

My template products should not be affected by these PHP issues. 

For the sake of my head/health, I need to take a break.

I'm pleased I didn't update again - there's far too many people posting issues for this to be updated until everything is sorted.  My sympathies go out to everyone affected, clients and devs.

Yes, thank you. @Andy Millne, thank you as well sir!

Again, thank you and I do apologize for my saltiness. You have to understand though that I witnessed the demise of vBulletin. It was tragic to be a part of and witness the decline of what was once preeminent. Please don't ever let that happen to you guys. You have the best product out there, keep it that way.

Yes, thank you. @Andy Millne, thank you as well sir!

Again, thank you and I do apologize for my saltiness. You have to understand though that I witnessed the demise of vBulletin. It was tragic to be a part of and witness the decline of what was once preeminent. Please don't ever let that happen to you guys. You have the best product out there, keep it that way.

No problem. I see thats now been sorted by one of our developers for you 🙂 

That wouldnt be the same in this case, as the user is getting a white page entirely.
Yes, that would be something you would need to speak to your VPN provider about really

Hello! Found something weird, not sure if anyone else is getting it or if I'm doing something wrong. But I have a Pages database with the Publish Date field activated. I'm trying to populate this database with backdated historical articles. The IPB system is letting me do this... eventually. But for the entire system to accept it I have to publish and edit the record several times.
Here are the replicable steps:
Step 1: Create new story as normal via Pages interface.

Step 2: Set Publish Date field to a past date, instead of 'immediately'.

Step 3: Publish. The system for some reason does not accept the past date, and instead acts as if we published this entry just now.

Step 4: Click the Prefix Tag ('Dreamcast', above the headline in the above image), which will take you to the Search section of the site listing entries matching the same tag. The newly-published article will be present, but its publish date will also be 'Just now' instead of in the past.

Step 5: Go back to the article, click 'Story actions > Edit'. Go to 'Publish Date' and re-enter the past date. Save. The article's date will be corrected.

Step 6: Again, click the prefix tag ('Dreamcast') and check once more the Search results for the tag. Even though the Pages entry's date has been fixed after the edit, the date listed on the search meta still acts as if it was recently posted.

Step 7: Go back one more time to the article, click 'Story actions > Edit', change nothing and just hit 'Save'. Go to the article in question, click the prefix tag one final time. Check the Search page results. The date has been fixed.

For some reason, going through the edit process a second time will correct the date on Search.
I imagine this isn't expected behaviour, but wanted to know if there was anything I could do about this or if it is simply a bug that needs fixing? Authors should only need to input the publish date of an entry once, but in order for it to work properly here the entry needs to be published, edited and then edited again. It's a bit much. 😅
Any ideas?

Its a very very broad error, so its likely not. Its simply saying the queue task broken, which could be anything at all that is running in background tasks

Sorry for your frustration here. I completely understand this when there are issues you cant get resolved on yoru site and need to move forward with those. 
Please allow me to explain a little further on the issue of patching individual sites. It's not always possible to resolve an issue with a fix which is created for a newer version of the software. Those fixes have not been tested on the version you are currently using (may actually cause you more harm than good), and may well require the upgrader to do things (for example, changing tables, updating templates, changing javascript) that can't be done by the simple updating of a file.
Let me get this into a ticket for you, and we can see if this is something that can indeed be applied to your site directly. Someone will be in contact as soon as they can

Yes I'm frustrated. I am mad at myself because I don't ever upgrade until I am confidently satisfied that issues with a release, that has gone through betas and should be safe to upgrade upon release but never is, have been addressed and it is safe to upgrade. Shame on me for being fooled. There is a lesson in all of this though... and that is that after I get the next stable version, it will be a looooong time before I upgrade again.

 
 
I read that other thread and your solution is akin to a non-starter is it not? Your solution is to allow for the plugins to be activated by the end user but if they are still breaking the site, what good does activating them do? I have to admit that I am laughing a bit here because of the incredulity of the offered solution. Am I misunderstanding the solution IPS has offered?
 
Honestly, there is no need to respond. Nothing is going to change. My broken site won't be fixed unless I upgrade and by upgrading, other aspects will break. WOW, what options I have!
The site is slightly broken and the offered solution is to break it in other places to fix what is currently broken. :facepalm:

WHAT? Are you -deleted what I really wanted to say here- kidding me? This borders on unacceptable.

I can't upgrade because your latest greatest will break other aspects and my site is currently broken because of a bad design in 4.7.1 and all you have to offer is, "we will need to pause then till you are willing to upgrade? I mean... really?  

Can you roll my site back to 4.7.0 with out losing any existing content?

Oye!
What is happening to IPS?
 

Yeah - i don't 'use it' but it works:
 

Update pushed to marketplace and pending approval.

Just to clarify, Classifieds is still compatible with 4.7.2, just not with PHP 8 and 4.7.2 together?

A new version has been uploaded to the Marketplace and is pending approval.
This version includes integration with Clubs.

5. Set up a group promotion to advance the NOOBs

5. Set up a group promotion to advance the NOOBs

Again, just me and what I might do in this scenario...

Select the last 20 or so pages (prior to those on a partial page load), just before where you want it to pick up, split them off into a different thread, lock the newly created thread for however long it takes you to move the prior posts from a partial listing page (and then opening the newly locked thread), so it can continue on in that context. Then as you get time, move the rest of the prior posts. At which point you will want to work forward so you get to select entire pages of posts.

Good luck!

Thank you for the additional information.
Unfortunately I need to crop the first part of the thread and not the end.  Perhaps I can come up with some SQL that will simply allow me to hide the posts

I don't believe they have addressed this matter as yet, someone will correct me if I am wrong.

I did add a minor edit to my post above incase you missed it.