Nathan Explosion

Have you thought that maybe they are just using your RSS feeds? No knowledge of your site, or the other one, so can't check if you have them enabled. But if you do then...

https://invisioncommunity.com/clientarea/

https://invisioncommunity.com/clientarea/

Delete the database
Delete the files
Reupload the files
Install the software.

https://www.ynwa.tv/files/file/20-ne-emoji-enhancements/
 

https://www.ynwa.tv/files/file/20-ne-emoji-enhancements/
 

Delete the database
Delete the files
Reupload the files
Install the software.

Seeing as there were some other people who reported this and were actually running an unsupported version of PHP...what version of PHP do you currently have in use? (view it on the Support page in the ACP)
If it is NOT 8.0 or 8.1, and is 8.2 or 8.3 then drop down to a support version (8.0 & 8.1)

Seeing as there were some other people who reported this and were actually running an unsupported version of PHP...what version of PHP do you currently have in use? (view it on the Support page in the ACP)
If it is NOT 8.0 or 8.1, and is 8.2 or 8.3 then drop down to a support version (8.0 & 8.1)

Crack on!

This will do absolutely nothing to stop copying images from your site. 
All it takes is Ctrl-U to see the page source including the image link, or a screen shot, a setting in some browsers to block right-click disabling, or using a browser extension.
More than stopping anyone, what you will accomplish is annoying people trying to use the back/forward/print/paste controls.  Also, because many screen readers require right-click, you're possibly running afoul of disability laws.
3 decades of failed blocking right clicks as "protection", yet it still persist! 
You're better off watermarking/digital fingering printing them then filing DMCA requests if they show up elsewhere.

Disabling the right click is not an effective way at all. There are countless ways to bypass that limitation (disable javascript, scrape the site, look at the image URL in the page's source, etc.). Personally, I think it's a waste of time even trying. 🙄
 
I'm unaware of any 3rd party plugin that does this, but there are several such examples if you just search for them (Google, Bing, etc). If you still want to go ahead with it, find some JavaScript code and add it to your theme.

Crack on!

It seems you were excessively helpful. You deserved it twice. 😂

You guys should really consider adding a maximum PHP version check both in the suite and the requirements checker. I'm not saying to lock everything with the wrong version, even a simple warning in ACP would to the job.
 
With a simple check for the maximum version, you'd avoid dozens of support requests... 🙄

Edit your conf_global.php file and change the http to https for your URL there.

It's clearly going to be a link on the default theme:

 
Easy to make it more obvious....

 
 
guest_post_pbr_blurb = "You can post now and register later."
guest_post_sign_in = "If you have an account, <a class='ipsType_brandedLink' href='{internal.front.app=core&module=system&controller=login.login}' data-ipsDialog data-ipsDialog-size='medium' data-ipsDialog-title='Sign In Now'>sign in now</a> to post with your account."
 

Confirmed as resolving the issue.

I'll be disabling that functionality until this is resolved then...just been alerted to a data leak (title of a private topic being visible) which is going to cause a few problems now that it's been seen.
Test of a topic in a private forum, viewable by a normal member...
 

Reporting it as it just occurred on my live site...
UPDATE `core_members_known_ip_addresses` `core_members_known_ip_addresses` SET `ip_address`='' WHERE ip_address != '' AND last_seen <1709136738 IPS\Db\Exception: Duplicate entry '0138fdaa72c8135e62b3487f5be7b11d-2970-' for key 'PRIMARY' (1062) #0 /home/fbaeefdf/live.ynwa.tv/system/Db/Db.php(1159): IPS\_Db->preparedQuery() #1 /home/fbaeefdf/live.ynwa.tv/applications/core/extensions/core/IpAddresses/Logins.php(33): IPS\_Db->update() #2 /home/fbaeefdf/live.ynwa.tv/system/Member/Member.php(6504): IPS\core\extensions\core\IpAddresses\_Logins->pruneIpAddresses() #3 /home/fbaeefdf/live.ynwa.tv/applications/core/tasks/pruneipaddresses.php(43): IPS\_Member::pruneAllLoggedIpAddresses() #4 /home/fbaeefdf/live.ynwa.tv/system/Task/Task.php(281): IPS\core\tasks\_pruneipaddresses->execute() #5 /home/fbaeefdf/live.ynwa.tv/applications/core/modules/admin/settings/advanced.php(751): IPS\_Task->run() #6 /home/fbaeefdf/live.ynwa.tv/system/Dispatcher/Controller.php(107): IPS\core\modules\admin\settings\_advanced->runTask() #7 /home/fbaeefdf/live.ynwa.tv/applications/core/modules/admin/settings/advanced.php(38): IPS\Dispatcher\_Controller->execute() #8 /home/fbaeefdf/live.ynwa.tv/system/Dispatcher/Dispatcher.php(153): IPS\core\modules\admin\settings\_advanced->execute() #9 /home/fbaeefdf/live.ynwa.tv/admin/index.php(13): IPS\_Dispatcher->run() #10 {main} I believe this is a knock-on effect of it NOT having been pruning the IP addresses correctly previously - the issue you'll have is that there could be multiple entries for a specific device_key and member_id, but with different IP addresses. Now that task has been fixed to do the pruning, when it tries to remove the IP address on those multiple entries, the PRIMARY key for each row will end up being the same as the key is made up of device_key, member_id, IP address (which is now blank)
Sample content attached:core_members_known_ip_addresses.sql
When the query in the task runs against that data, the error occurs:
UPDATE `core_members_known_ip_addresses` `core_members_known_ip_addresses` SET `ip_address`='' WHERE ip_address != '' AND last_seen <1709135288
 
 

Reporting it as it just occurred on my live site...
UPDATE `core_members_known_ip_addresses` `core_members_known_ip_addresses` SET `ip_address`='' WHERE ip_address != '' AND last_seen <1709136738 IPS\Db\Exception: Duplicate entry '0138fdaa72c8135e62b3487f5be7b11d-2970-' for key 'PRIMARY' (1062) #0 /home/fbaeefdf/live.ynwa.tv/system/Db/Db.php(1159): IPS\_Db->preparedQuery() #1 /home/fbaeefdf/live.ynwa.tv/applications/core/extensions/core/IpAddresses/Logins.php(33): IPS\_Db->update() #2 /home/fbaeefdf/live.ynwa.tv/system/Member/Member.php(6504): IPS\core\extensions\core\IpAddresses\_Logins->pruneIpAddresses() #3 /home/fbaeefdf/live.ynwa.tv/applications/core/tasks/pruneipaddresses.php(43): IPS\_Member::pruneAllLoggedIpAddresses() #4 /home/fbaeefdf/live.ynwa.tv/system/Task/Task.php(281): IPS\core\tasks\_pruneipaddresses->execute() #5 /home/fbaeefdf/live.ynwa.tv/applications/core/modules/admin/settings/advanced.php(751): IPS\_Task->run() #6 /home/fbaeefdf/live.ynwa.tv/system/Dispatcher/Controller.php(107): IPS\core\modules\admin\settings\_advanced->runTask() #7 /home/fbaeefdf/live.ynwa.tv/applications/core/modules/admin/settings/advanced.php(38): IPS\Dispatcher\_Controller->execute() #8 /home/fbaeefdf/live.ynwa.tv/system/Dispatcher/Dispatcher.php(153): IPS\core\modules\admin\settings\_advanced->execute() #9 /home/fbaeefdf/live.ynwa.tv/admin/index.php(13): IPS\_Dispatcher->run() #10 {main} I believe this is a knock-on effect of it NOT having been pruning the IP addresses correctly previously - the issue you'll have is that there could be multiple entries for a specific device_key and member_id, but with different IP addresses. Now that task has been fixed to do the pruning, when it tries to remove the IP address on those multiple entries, the PRIMARY key for each row will end up being the same as the key is made up of device_key, member_id, IP address (which is now blank)
Sample content attached:core_members_known_ip_addresses.sql
When the query in the task runs against that data, the error occurs:
UPDATE `core_members_known_ip_addresses` `core_members_known_ip_addresses` SET `ip_address`='' WHERE ip_address != '' AND last_seen <1709135288
 
 

I'll be disabling that functionality until this is resolved then...just been alerted to a data leak (title of a private topic being visible) which is going to cause a few problems now that it's been seen.
Test of a topic in a private forum, viewable by a normal member...
 

If you are using Windows Defender then report it as a false positive back to Microsoft:
https://www.microsoft.com/en-us/wdsi/filesubmission/

I'll be disabling that functionality until this is resolved then...just been alerted to a data leak (title of a private topic being visible) which is going to cause a few problems now that it's been seen.
Test of a topic in a private forum, viewable by a normal member...