NoSpy

Hello I have to create a website for a club but only registered members will be able to see the content. Maintenance mode is very practical but problematic because when I need to update the website I have to block the site with htaccess or modify the DNS. My second problem is that even if the website is in maintenance mode, the robots manage to index content that has never been made public, which is very problematic. My question is how to create a private community that is only accessible to members without activating maintenance mode who blocks the future member's ability to pay for the subscription?

I don't know where to go to answer the support ticket, here it's not support?

I've already tried it several times and the result is always the same, it's one of the files I've given up on moving.

When I move a category, I make a backup between each interaction. I've had to restore the website more than 12 times because the moves don't finish, some images are moved while others are still in the old folder like imageproxy. For gallery it's more problematic, your script modifies the CHMOD of the folders making them inaccessible requiring you to contact the host so that he can modify the rights and finally realize that the root folder of gallery has been corrupted, resulting in a partial loss of documents and files requiring you to restore the website.

I finished the full backup.

The site has been closed since June 15, pending resolution of the problem. I'll need your IP address for the firewall (PM).

Hello, It doesn't work completely, once again I have data loss, for example imageproxy and gallery are not transferred to the new location.

I have sended message to PM 👍

Yes

MyISAM DYNAMIC: ALTER TABLE `downloads_ccontent` InnoDB DYNAMIC: ALTER TABLE `downloads_ccontent` Edit : What do I need to delete from this table - is it empty?

I've checked with my other hosts, none of which offer this feature except on the dedicated server, and I don't see why you insist on it. The hosting provider fully supports DYNAMIC InnoDB and MyISAM as you can see : https://files.nospy.ch/BUG/IPS/2023-0620/MyISAM-03-InnoDB.txt The original question is that I'm unable to modify some tables MyISAM to InnoDB here's the list : https://files.nospy.ch/BUG/IPS/2023-0620/MyISAM-01-InnoDB.jpg This table MyISAM is empty or nearly so, and it's impossible to modify to InnoDB it without getting this error.

The host will not make any changes as demand is too low (2 clients only), we have also seen some loosening. MyISAM DYNAMIC and InnoDB COMPACT = SQL 88MB MyISAM DYNAMIC and InnoDB DYNAMIC = SQL 312MB If new table are created InnoDB COMPACT and I have change manualy to DYNAMIC https://files.nospy.ch/BUG/IPS/2023-0620/MyISAM-03-InnoDB.txt

I have checked and all tables using DYNAMIC for InnoDB or MyISAM. https://files.nospy.ch/BUG/IPS/2023-0620/MyISAM-01-InnoDB.jpg https://files.nospy.ch/BUG/IPS/2023-0620/MyISAM-02-InnoDB.jpg My host by default set "InnoDB COMPACT" and "MyISAM DYNAMIC". It's possible add in global config ? $INFO['mysql_tbl_type'] = 'InnoDB'; $INFO['mysql_tbl_type'] = 'DYNAMIC';

We had made a back-up but didn't immediately realize that some files were missing. On another product I have several functions to clean up the database or remnants files. It should be possible to reset a comparison between database and storage. Find and delete all orphan (unused) tags - BD only. Find all posts not attached to a valid category + optional deletion with attached objects - BD only. Find all slugs not attached to an Item + optional deletion - BD only. Find and delete all orphaned comments (not attached to an Item) - Disc & BD. Find and delete all orphaned comment attachments - Disk & DB. Find and delete all orphaned File objects (not corresponding to a file on disk) - BD only. Find and delete all orphaned file roots (not attached to a Collection or User) and their contents (recursively) - Disk & DB. Recreate all item slugs (change canonical title slugs-[0-9] to a slug generated from the current title). The old slugs will still work, but will redirect to the new ones. I've noticed that there's a big information gap in the SQL database, which still has tables that shouldn't exist anymore.

After modifying each table individually, I have few table refuse changing MyISAM to InnoDB with error like this : The list of SQL tables that generate an error https://files.nospy.ch/BUG/IPS/2023-0620/MyISAM-01-InnoDB.jpg How fix that ?