I have a couple of sites who were using ECT and have stopped selling from their sites (for now). They may (or may not) go back to selling at some point. Here is my question - is there any problem in simply not using the store pages/files but keeping them on the server. I'm wondering if I would still have to update them to new versions - not for new features, but for any security vulnerabilities? Is there a file or files, I could temporarily remove or rename to keep it safe -- but not have to through the entire process of uploading and starting over if and when they decide they want to sell again?

Thanks!

Hi

How about a plugin like this https://wordpress.org/plugins/wp-maintenance-mode/

Andy

Please feel free to review / rate our software

I didn't explain correctly - they only want to stop selling items on their site - the rest of their site will remain as is and live.

You could remove buy & checkout buttons across the whole site with this line in includes.php. Doing so will still show the products with their price.

$nobuyorcheckout=TRUE;

And you can also disable the prices with

$noprice=TRUE;

They don't want store pages to display at all. What I want to do is leave the store (pages, files, database) on the server, but not have to worry about keeping it updated (with new versions - for security updates). It will just sit there in the background until a later date, when the client decides to go back and start using it again. The rest of their site will remain in tact and live for site visitors, they just won't have a store at all.

Does this make sense? Or...can I just remove all links to the store and not worry that I'm not updating to new versions since it's not being used? What files could be vulnerable?

A htaccess 302 temporary redirect for the products, proddetail & categories, cart, search pages etc is a possible option , but I'm no expert in how that will affect the sites ranking with search engines.

In respect of the updaters, I'd not be comfortable with no updates purely from the security aspect with keeping the database available even though the site wouldn't be using the dynamic side of things

Will - Bolton Manchester UK