we also do some caching of group view, so want to do some testing there too…

Ok, I checked out the control panel and there was some “supercaching” that was active and I tried to make sure that EVERYTHING was turned off now.

But, the problem didn’t go away 🙁

yeah, I am beginning to think there is an issue with our group view query when using single group ids… seeing some weird stuff in my testing…

would you be willing to try a couple code changes?  note, keep copies, this is fully untested but think it might help you…

in file simple-press/forum/content/classes/sp-group-view-class.php, around line 225 find this line

if (!$records) {

and change it to

if (!$records || !empty($groupids)) {

and then around line 258 find this line

if ($records) sp_add_cache('group', $records);

and change it to

if ($records && empty($groupids)) sp_add_cache('group', $records);

now, this will not be the final change if this turns out to be a problem, but for your specific case, it might work…   probably very premature to ask for this change, but will be very good data for us…

I made the changes, cleared the forum cache, but still no go …

did you adjust the group view query in your child theme?

also, you might need to clear the group view cache on forum – toolbox – housekeeping to reset everything…

might be easier if you could give us ftp access so we can mod files and look at stuff… understand if thats not doable…  if so, pm the details to both andy and steve…  

I just sent you the info.

I dont see the changes that I had requested… I made them, plus one more..

Can you take a look?  seems to be working now… 

YES, it works!  I must have made the changes in the wrong file 🙁

I’m so glad, hopefully it’ll still work tomorrow!

THANKS!

me too!  please let us know… knew it was caching 😉 just not ours 😎 

will roll this change into next release…

I’m literally crying.

Sent the link to the fire district to the local paper, tried it myself and we’re back to were we were half a year ago.  Apparently when I upgraded yesterday I lost your fix.

To add insult to injury, I had to PAY to be able to report this bug AGAIN.

Cleverly, the Bronze membership was removed.

So I’m looking to pay $45 so this bug can get fixed AGAIN.

I go through the whole process, was clever enough to detect how to NOT auto renew, put in my credit card info, get an error for the robot thing, AGAIN unchecked the auto renewal, entered my credit card info again and SURPRISE!!!!

I got charged $135!!!

Hi:

We’ve issued a refund for your purchase and cancelled the membership.  Please feel free to repurchase the membership you need.

Copper and Bronze memberships were removed because they were priced ridiculously low and did not reflect the cost of providing support services.  10.00 for unlimited hours of support for 30 days was a little ridiculous so it was removed.  At that rate our very experienced developers were working for pennies per hour which is just, well, insane.

Thanks.

Thanks, so I now paid $45 so you’ll hopefully fix it again:

correct – per the change log, it was a minor security issue only release…  we will be coming out with 6.0 before much longer (October) which has the fix… so unfortunately, you will have to remake that change until then… sorry…

Copper and Bronze memberships were removed because they were priced ridiculously low and did not reflect the cost of providing support services. 10.00 for unlimited hours of support for 30 days was a little ridiculous so it was removed. At that rate our very experienced developers were working for pennies per hour which is just, well, insane.

I agree, that’s insane.  But what do you call it when you get paid NOTHING for the work and in fact you have to PAY for the privilege to work?

I actually have not the slightest idea what to do.