[geeklog-devel] geeklog-devel Digest, Vol 110, Issue 4

Fri Nov 13 10:55:36 EST 2015

Tom,

Yes, I think a hard coded route to turn on/off features would work best. 
That way there is no way for cretins to get into the backend of the 
configuration to view or mess with the settings.  An approach to 
automatically rest the site is a great idea, instead of running an 
individual cron file to do this would help, especially those when there are 
so many different server configurations.

Having a segregated section in the siteconfig to let webmasters know where 
all this info can be found would also be beneficial.  So your first idea 
would work okay with me.  Just having the list array for true/false for all 
the options for Demo would be awesome.

You already know I run the Demo site for Geeklog and would be an ideal 
starting point to test out your thoughts how things progress.  Plus you 
already have FTP access to the server for that site.

Michael

-----Original Message----- 
From: geeklog-devel-request at lists.geeklog.net
Sent: Friday, 13 November, 2015 01:32
To: geeklog-devel at lists.geeklog.net
Subject: geeklog-devel Digest, Vol 110, Issue 4

Send geeklog-devel mailing list submissions to
geeklog-devel at lists.geeklog.net

To subscribe or unsubscribe via the World Wide Web, visit
https://pairlist8.pair.net/mailman/listinfo/geeklog-devel
or, via email, send a message with subject or body 'help' to
geeklog-devel-request at lists.geeklog.net

You can reach the person managing the list at
geeklog-devel-owner at lists.geeklog.net

When replying, please edit your Subject line so it is more specific
than "Re: Contents of geeklog-devel digest..."

Today's Topics:

   1. Geeklog Demo Mode (Tom)
   2. Re: Geeklog Demo Mode (Wim Niemans)

----------------------------------------------------------------------

Message: 1
Date: Thu, 12 Nov 2015 10:14:57 -0500
From: "Tom" <websitemaster at cogeco.net>
To: "'Geeklog Development'" <geeklog-devel at lists.geeklog.net>
Subject: [geeklog-devel] Geeklog Demo Mode
Message-ID: <012201d11d5c$e4789700$ad69c500$@cogeco.net>
Content-Type: text/plain; charset="us-ascii"

If I have time I would like to add some sort of demo mode  to the next
version of Geeklog.

I see a demo mode as a site used for testing and evaluating by the general
public. It will be refreshed every X minutes by some other process by
dropping and importing the database and either deleting and adding the files
again or refreshing just certain directories. The Admin user of a demo site
has its security rights reduced automatically.

Now I don't want this to be a huge endeavor but I would like it to include
as many useful features as possible. Possible features include:

- Configuration. Hide completely and read only modes for Configuration Tabs
and options
- Allow read only modes for things like Plugin Admin, DB Backups, etc... (or
at least disable certain features like plugin uploads, etc..)
- Allow read only of Users and Groups OR somehow lock down or hide the key
users and security features while still letting visitors create test users
and groups
- Develop this in mind so 3rd party plugins like the forum could take
advantage of the demo mode.

1) My first thoughts is that you would enable the DEMO_MODE variable in the
siteconfig.php and then add a bunch of if statements like below anywhere in
the Geeklog core code we want to control what the demo mode has access to.

We could go a bit farther with this idea and add a demo mode array with
different features set to true or false which would allow the admins to
change things as needed. This could get a bit mucky in the configuration
though.

if ( defined('DEMO_MODE') ) {
    redirect_header($_CONF['site_url']."/index.php",10,'Uploads are disabled
in demo mode');
    exit;
}

2) My second idea would be in the install allow for the creation of a
DemoAdmin account (along with updated articles, etc... to reflect demo mode)
with the appropriate security features enabled which would use Geeklog's own
security to control access. The Admin account for the site would still be
the root user and private but the DemoAdmin account would be what is used by
vistors to test things out. Doing this would mean we would need to add more
security features to Geeklog to be able to control certain things like read
only access to the plugin admin. The difficulties here would be the
Configuration. We already have security for access to tabs or not. Allowing
for viewing only for certain tabs and security options would be a lot more
work and make the groups access list grow extremely long.

These are just only ideas and I may not have time to work on it right away
but does anyone have any thoughts on the subject?

Tom

References:
http://wiki.geeklog.net/index.php/Setting_up_a_Demo_Site
http://project.geeklog.net/tracking/view.php?id=1059
http://eight.pairlist.net/pipermail/geeklog-devel/2009-January/004000.html

------------------------------

Message: 2
Date: Thu, 12 Nov 2015 18:03:22 +0100
From: Wim Niemans <niemans at nlbox.com>
To: Geeklog Development <geeklog-devel at lists.geeklog.net>
Subject: Re: [geeklog-devel] Geeklog Demo Mode
Message-ID: <C1184769-483A-4E8A-940D-1ACD30FEA9B0 at nlbox.com>
Content-Type: text/plain; charset=utf-8

For my plugin(s) I am using a sandbox mode.
If the constant is defined, than

? skip all sql updates and issue a message
? generate a test submit button in forms that redirects the form to a stub 
that lists GET, POST, FILES etc.

Just a thought. I am using this mainly for development.
Not to say that I have standard a debug area on the page, that, when 
activated, lists all debug of the script.

Cheers,
wim niemans

> Op 12 nov. 2015, om 16:14 heeft Tom <websitemaster at cogeco.net> het 
> volgende geschreven:
>
> If I have time I would like to add some sort of demo mode  to the next
> version of Geeklog.
>
> I see a demo mode as a site used for testing and evaluating by the general
> public. It will be refreshed every X minutes by some other process by
> dropping and importing the database and either deleting and adding the 
> files
> again or refreshing just certain directories. The Admin user of a demo 
> site
> has its security rights reduced automatically.
>
> Now I don't want this to be a huge endeavor but I would like it to include
> as many useful features as possible. Possible features include:
>
> - Configuration. Hide completely and read only modes for Configuration 
> Tabs
> and options
> - Allow read only modes for things like Plugin Admin, DB Backups, etc... 
> (or
> at least disable certain features like plugin uploads, etc..)
> - Allow read only of Users and Groups OR somehow lock down or hide the key
> users and security features while still letting visitors create test users
> and groups
> - Develop this in mind so 3rd party plugins like the forum could take
> advantage of the demo mode.
>
>
> 1) My first thoughts is that you would enable the DEMO_MODE variable in 
> the
> siteconfig.php and then add a bunch of if statements like below anywhere 
> in
> the Geeklog core code we want to control what the demo mode has access to.
>
> We could go a bit farther with this idea and add a demo mode array with
> different features set to true or false which would allow the admins to
> change things as needed. This could get a bit mucky in the configuration
> though.
>
> if ( defined('DEMO_MODE') ) {
>    redirect_header($_CONF['site_url']."/index.php",10,'Uploads are 
> disabled
> in demo mode');
>    exit;
> }
>
> 2) My second idea would be in the install allow for the creation of a
> DemoAdmin account (along with updated articles, etc... to reflect demo 
> mode)
> with the appropriate security features enabled which would use Geeklog's 
> own
> security to control access. The Admin account for the site would still be
> the root user and private but the DemoAdmin account would be what is used 
> by
> vistors to test things out. Doing this would mean we would need to add 
> more
> security features to Geeklog to be able to control certain things like 
> read
> only access to the plugin admin. The difficulties here would be the
> Configuration. We already have security for access to tabs or not. 
> Allowing
> for viewing only for certain tabs and security options would be a lot more
> work and make the groups access list grow extremely long.
>
> These are just only ideas and I may not have time to work on it right away
> but does anyone have any thoughts on the subject?
>
> Tom
>
> References:
> http://wiki.geeklog.net/index.php/Setting_up_a_Demo_Site
> http://project.geeklog.net/tracking/view.php?id=1059
> http://eight.pairlist.net/pipermail/geeklog-devel/2009-January/004000.html
>
>
> _______________________________________________
> geeklog-devel mailing list
> geeklog-devel at lists.geeklog.net
> https://pairlist8.pair.net/mailman/listinfo/geeklog-devel
>

------------------------------

Subject: Digest Footer

_______________________________________________
geeklog-devel mailing list
geeklog-devel at lists.geeklog.net
https://pairlist8.pair.net/mailman/listinfo/geeklog-devel

------------------------------

End of geeklog-devel Digest, Vol 110, Issue 4
********************************************* 