PPlanet

This is sort of related but I cannot find the topic where it was discussed. Like the OP, I also have images not attached but linked directly in thousands of posts, coming from the monthly folders under Uploads, whose urls are often copied manually when opening images from the gallery albums in a separate tab. So you get an url like this for example: https://domain.com/uploads/monthly_2024_09/large.275220.jpeg.7ca4cd251d1d7a02c980939745bc95d7.jpeg Did I read correctly that in version 5, those "monthly" folders will be discontinued? And if so, what happens to the existing ones (like in my example the "monthly_2024_09")? Do they remain there? Because if not I foresee a disaster of broken links among posts; unless the system automatically modifies the path. Could you please clarify? And I apologise in advance if I misunderstood anything about the plan going forward. Cheers.

To upgrade to 4.7.19 can I still run database 5.7 and still have mixed tables InnoDB/MyISAM? Will I get a simple warning about V5 or will this upgrade already force me to change something? (I'm not planning to upgrade to version 5 for quite a while yet, so I don't want to be changing anything just yet)

It's all good at the moment @Marc. What I meant is that clearing the system cache did the trick for me (then again, not sure if it was the same problem others were having). I do use Cloudflare too, so maybe that's another factor which may have had some incidence. If it happens again, I'll let you know; cheers.

No, nothing related to that.

What I noticed on my forum is that out of the blue, the tweets would just not display. I cleared the system cache and they are displaying again. Not sure if this is the same problem the OP was having.

There is a third party app for that, but I don't advice to guide yourself by IP addresses duplicates, because of the reasons @Dll mentions above. And the bigger your membership base, the worse it gets. That same app also can detect and prevent registrations from people using a same device, which is a better way to go IMHO. Sadly, the functionality for device detention and subsequent actions it offers is not as good as what it offers for IP address detection. You still need to go fishing for the duplicate devices from a list instead of sending you a message letting you know of a case when it happens (which I believe it does when there's an IP address match). The was a previous app by another author that was more practical and sent messages when it came to device detention but he discontinued it.

Okay, thanks @Marc Stridgen. That's what I thought. Cheers.

Hi @Marc Stridgen, can I PM you a couple of examples?

On my site there seem to be quite a difference between the maximum amount of visitors to members' profiles displayed in the latest visitors block. While some show up to 11, others only show up to 5, and of course I'm only comparing profiles for members I know must have received more visits than either amount. So, I'm trying to work out the reason behind this difference, if there's some setting somewhere that determines the max. number of visitors shown for each profile. At this point I tend to believe that only members who signed up before a certain date, show up to 11 visitors, while those who signed up after show up to 5. I know that would odd but it's the only explanation I've found so far. Any ideas?

@sean182011 not sure if I understand correctly. Yes you can achieve that with permissions but you'll also need to approve all registrations manually. You can select that under Settings > Login & Registration So, they won't become a member until you approve their accounts. But is it that what you want to achieve? Basically nobody becoming a member until manually approved? Or even after being approved, still not being able to see more than a guest? I still don't have that quite clear after reading your post. For the latter, the most practical solution would be giving your default member group (generally group #3) limited permissions. So, when they move from "guests" to "members" they only see what you want them to see, and only after that they begin moving to other usergroups with more permissions, either manually by you moving one by one or by promotion rules (which is generally a better way). Mind you, this solution is better applied when you are creating your site, so from the beginning the member group (which you can give any name really) serves that purpose. The way around if your forum already exists and you have members already would be, before implementing the above, to mass move all your members to a higher usergroup. You start by copying the "members" group and then moving members to the newly created group that you can call whatever you want too. Anyway, if I misunderstood, please let me know.

@Adam Chernoff, you may want to take a look at these third party apps: https://www.invisioneer.org/files/file/23-dp45-guest-view-limits/ https://www.invisioneer.org/files/file/24-dp45-groups-view-limits/ Particularly if you want to have a teaser system to allow guests or members of some usergroups to have a limited access to topics, rather than all or nothing.

These three should be fine, as I have them and had no problem with them. The Classifieds app needs to be updated though. I opened a ticket on bbcode.it and now I'm waiting, as the scanner did lock that app. Luckily I was able to perform the IPS upgrade to 4.7.15 without interruptions (it simply locked that app after the upgrade was completed), and being this on my test installation, it's not a major problem. But I'll wait for that app to be updated before upgrading my live site to the lastest version.

So, is this a case that if upgrading IPS to 4.7.15, one needs to upgrade third party apps before? (I mean to avoid being stuck half way an upgrade?)

Thanks Wicked, but I believe that in that case you should have come across the scanner before. Version 4.7.3 was the last version that worked with PHP 7.4 and it came with the scanner to help you prepare for the PHP 8-compatible versions. I asked because if you were upgrading from something older than 4.7.3, you could have simply switched back your PHP to 7.4, uninstall the files, and then change back to PHP 8 after the upgrade. Now, it worries me that it seems that the scanner on 4.7.15 seems to be detecting potential problems not detected by immediately earlier versions. I'm saying this based on this topic and others commenting about having trouble with the upgrade due to third party apps that now they cannot uninstall, etc.

@Wicked007, may I ask from what version you are upgrading from? Is this the first time you upgrade to a version with the PHP8 scanner?