--
You received this message because you are subscribed to the Google Groups "opensiddur-tech" group.
To unsubscribe from this group and stop receiving emails from it, send an email to opensiddur-te...@googlegroups.com.
To post to this group, send email to opensid...@googlegroups.com.
Visit this group at https://groups.google.com/group/opensiddur-tech.
For more options, visit https://groups.google.com/d/optout.
I just checked the site, and it appears to be working. There is a piece of advice I'd like to offer, and I hope I am not out of place.
Based on what is stated below, it appears as if the site is not being backed up regularly, or at least not being properly backed up before any hardware or software upgrades are taking place. I would recommend double-checking your host's back-up policies as they will handle that to a point, but will usually not perform daily or weekly backups and leave that to the user. If you're interested I'd be willing to host the Open Siddur WordPress site at no charge, since I benefit greatly from the project and have done so for years now. I provide twice-daily restore points as well as backup/restore on demand as a matter of policy since a lot of my clients are healthcare-related and so require extra efforts at data protection and security.
I still plan to contribute code-wise to the accessibility of the Open Siddur application itself. Time, however, up to this point has not permitted this. It's getting a bit less crowded though so I plan to clone the project this week and start working on it.
Amanda
Re: database upload limit via phpMyAdmin, you can try asking your host to temporarily increase it to allow you to upload. If that doesn't worok, (sometimes they will refuse to do this, and I do unless there is a very specific reason since on my host the limit is 500MB), they should be willing to take a zip of the database and import it using the ClI. Re: DB user and specific password for that user: this is how that user/password combo should be managed, plus granting it all necessary privileges for the database. You'll also want to redo your salts and hashes for the wp-config file if you haven't done so already, since essentially this is a new database/databases for each site. And yes, separating the sites into their own databases is a good idea. while you can have more than one WordPress site installed in a single database, it's kind of like WordPress Multisite: Rule number one is don't do it unless there is a really good reason because it's going to end up creating a lot more work.
Amanda
Regarding your admin users:
Does the installation still have them listed as admin/all capabilities, or have those been changed? The easiest way to check this is to look within the "users" section of the admin panel. You, as an admin user, should be able to restore their roles if necessary. If you set up a new WordPress install, and you don't check the default role of new users before importing the database, their role will be set to the default role for new users, which is subscriber out-of-the-box. YOu'll also want to make sure that each user is resent a password reset message, as WordPress does not store passwords in plain text, so there is no way for passwords to be imported/preserved.
Amanda
Can you check your prefix_usermeta table, specifically the
wp_capabilities meta key to ensure that the capabilities are
correct for the users in question? This is painful but the final
resort is to delete the users and then recreate them, which raises
the problem of temporarily re-assigning their posts to another
author and then assigning them back for each. Note that prefix is
usually wp, but will be different if there is more than one
WordPress instance using the DB, and out-of-box user roles are
stored as serialized arrays in wp_usermeta under wp_capabilities.
Example array: a:1:{s:13:"administrator";b:1;}
Amanda