CONFIDENTIAL Daily /live-demo/ check instructions

This article lists the actions that checks the functionality of /live-demo/ environment. 

Purpose:

The purpose of live-demo is to provide a quick demonstration on how the plugin works, so users can very quicky try how things work, ideally with some content ready and uploaded to media gallery and some examples of animations that were done before.

Background

The live-demo area is a blank wordpress installation, with pre-installed plugin and a single user "demo" with password "demo". The demo user has editor rights, so he can add media, create new sequences etc. There is a adminimize plugin installed, that hides or restrict access to parts of wp-admin which are not useful for live-demo of the plugin. 

Issue:

Because every customer, that wants to use the live-demo is loggin into the same user, the settings, view changes and all other settings are kept from what the previous customer has entered. 

For example if someone changes the color settings inside wp-admin, those settings will be saved and if the next customer logs in a demo user, he will see the different color of wp admin. 

Solution: (manual)

To check the basic settings are correct in the wp-admin are. 

1) Navigate to scrollsequence.com/live-demo/wp-admin 

2) Check that password has not been changed using the demo:demo login:pass combination. If you find someone has changed the password, please contact me and I will reset it. 

3) Check media gallery - anyone can upload any image, so periodically check, that nothing offensive has been uploaded. If yes, delete media gallery image and associated sequences. 

4) Check UI Layout - Sometimes users drag around the metaboxes. Those drags are then saved, leaving the wrong layout for next user. See below for examples. If someone has broken the layout, please correct as per below and hit Update button to save the layout. 

It would be great to do this check daily there is some free time to do this. 

Did this answer your question? Thanks for the feedback There was a problem submitting your feedback. Please try again later.