A list of unordered use-cases, will be reordered once it is clear what this document should contain.
If something goes terribly wrong (e.g. attacks on the site) it is best to take the site offline so that the database, our most valuable data, doesn't get damaged. Depending on which passwords or access data you have at hand, these two options may be applied, the first being the safer one, the second at least displaying a status message a la site offline.
Currently we are keeping a backup of every hour for the last 24 hours, and a backup of every day for the last 14 days, so it should be possible to roll back the database to a point where the data was ok and not loose too much content.
Don't forget to contact vvvvebmaster if something like this happens. (+49 179 4586372).
Shop settings are here admin/settings/licensing
Nodereference update script is here: admin/settings/nodereference
Edit banners here: banners
Edit excluded auto-import usernames here: admin/settings/blog%20autoimport
go to a page -> edit then replace "edit" with "access-statistics", like so:
node/91772/access-statistics
If you need to edit a user, you may do so at /users/<name>/edit-settings. The following information can be changed here:
An overview of all users in the backend is here: admin/user/user/advuser
In Drupal collection of tags are called "Vocabularies". Categorizing in general is referred to as the "Taxonomy Sytem".
Tags are best handled by using the Taxonomy Manager. Useful operations supported by the taxonomy manager are:
For cleaning up tags in freetagging vocabularies there basically are two important functions:
admins (master+joreg) can logon as a different user if they want to see the same problems they are having with the site. Just go to /devel/switch/<username>. Will only work when the devel module is turned on.
Simply go to:
Edit User Settings
on a users page and change the Username there. Save. That's it.
*
anonymous user login
~1d ago
~1d ago
~2d ago
~4d ago
~15d ago
~24d ago
~29d ago
~1mth ago
~1mth ago
~1mth ago