From dirk at haun-online.de  Mon Nov  2 14:59:46 2015
From: dirk at haun-online.de (Dirk Haun)
Date: Mon, 2 Nov 2015 20:59:46 +0100
Subject: [geeklog-devel] Geeklog.net Upgraded
In-Reply-To: <E20648CF-0978-49E9-AEFE-9D922C455028@haun-online.de>
References: <000001d1119e$d600d9e0$82028da0$@cogeco.net>
 <E20648CF-0978-49E9-AEFE-9D922C455028@haun-online.de>
Message-ID: <3CBDA671-0548-42AC-9146-96010A92ABD5@haun-online.de>

FYI:

> And then I noticed that a new Jenkins version is available, but it requires a newer Java version than the one we have on the server. Guess I have to ask pair.com to install Java 7 for us.

Turns out Java 7 was already installed but needed a few tweaks to get it to work with Jenkins (or the other way around).

Anyway, our Jenkins is running the latest LTS version again now.

Dirk


-- 
https://www.themobilepresenter.com/



From websitemaster at cogeco.net  Tue Nov 10 10:21:51 2015
From: websitemaster at cogeco.net (Tom)
Date: Tue, 10 Nov 2015 10:21:51 -0500
Subject: [geeklog-devel] [SUSPECTED SPAM] Geeklog v2.1.1 Beta 1 Email Bug
	and Language Files
Message-ID: <03bf01d11bcb$864b5510$92e1ff30$@cogeco.net>

For those of you using the beta just a note that there is a bug that
prevents the user email form from sending out an email.  It is now fixed in
the repository.

Also Ben if you have time (or anyone else who speaks French) can we get the
French language file updated? It shouldn't take too long. Also the forum
French language file could use some updates ;-)

The same goes for the Japanese language file.  I had to add a few more
language variables with my last commit.

Finally, I think Geeklog v2.1.1 Beta 1 is pretty solid. Should we have the
final release for this version happen next week or should we wait another
week?

Thanks

Tom



From geeklog at mystral-kk.net  Tue Nov 10 18:18:46 2015
From: geeklog at mystral-kk.net (geeklog at mystral-kk.net)
Date: Wed, 11 Nov 2015 08:18:46 +0900 (JST)
Subject: [geeklog-devel] Geeklog v2.1.1 Beta 1 Email Bug and Language
 Files
In-Reply-To: <03bf01d11bcb$864b5510$92e1ff30$@cogeco.net>
References: <03bf01d11bcb$864b5510$92e1ff30$@cogeco.net>
Message-ID: <49470.203.189.105.202.1447197526.squirrel@www.s215.xrea.com>

Tom wrote:

> For those of you using the beta just a note that there is a bug that
> prevents the user email form from sending out an email.  It is now fixed
> in
> the repository.
>
> Also Ben if you have time (or anyone else who speaks French) can we get
> the
> French language file updated? It shouldn't take too long. Also the forum
> French language file could use some updates ;-)
>
> The same goes for the Japanese language file.  I had to add a few more
> language variables with my last commit.

I updated the Japanese language file.

> Finally, I think Geeklog v2.1.1 Beta 1 is pretty solid. Should we have the
> final release for this version happen next week or should we wait another
> week?

It would be better to send out a release candidate now.
--
Kenji ITO
http://mystral-kk.net




From websitemaster at cogeco.net  Wed Nov 11 10:55:21 2015
From: websitemaster at cogeco.net (Tom)
Date: Wed, 11 Nov 2015 10:55:21 -0500
Subject: [geeklog-devel] Geeklog v2.1.1 Beta 1 Email Bug and Language
	Files
In-Reply-To: <49470.203.189.105.202.1447197526.squirrel@www.s215.xrea.com>
References: <03bf01d11bcb$864b5510$92e1ff30$@cogeco.net>
 <49470.203.189.105.202.1447197526.squirrel@www.s215.xrea.com>
Message-ID: <00c601d11c99$5ed50d90$1c7f28b0$@cogeco.net>

Thanks.

I have updated Geeklog.net with the latest changes.

Dirk can you run the script to synch the language files again?


Tom

-----Original Message-----
From: geeklog-devel [mailto:geeklog-devel-bounces at lists.geeklog.net] On
Behalf Of geeklog at mystral-kk.net
Sent: Tuesday, November 10, 2015 6:19 PM
To: Geeklog Development <geeklog-devel at lists.geeklog.net>
Subject: Re: [geeklog-devel] Geeklog v2.1.1 Beta 1 Email Bug and Language
Files

Tom wrote:

> For those of you using the beta just a note that there is a bug that 
> prevents the user email form from sending out an email.  It is now 
> fixed in the repository.
>
> Also Ben if you have time (or anyone else who speaks French) can we 
> get the French language file updated? It shouldn't take too long. Also 
> the forum French language file could use some updates ;-)
>
> The same goes for the Japanese language file.  I had to add a few more 
> language variables with my last commit.

I updated the Japanese language file.

> Finally, I think Geeklog v2.1.1 Beta 1 is pretty solid. Should we have 
> the final release for this version happen next week or should we wait 
> another week?

It would be better to send out a release candidate now.
--
Kenji ITO
http://mystral-kk.net


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



From dirk at haun-online.de  Wed Nov 11 11:17:03 2015
From: dirk at haun-online.de (Dirk Haun)
Date: Wed, 11 Nov 2015 17:17:03 +0100
Subject: [geeklog-devel] Geeklog v2.1.1 Beta 1 Email Bug and Language
	Files
In-Reply-To: <00c601d11c99$5ed50d90$1c7f28b0$@cogeco.net>
References: <03bf01d11bcb$864b5510$92e1ff30$@cogeco.net>
 <49470.203.189.105.202.1447197526.squirrel@www.s215.xrea.com>
 <00c601d11c99$5ed50d90$1c7f28b0$@cogeco.net>
Message-ID: <8C21A5D1-7414-42B5-9403-C3DAFB8162ED@haun-online.de>

Tom wrote:

> Dirk can you run the script to synch the language files again?

Done. Committed & pushed.

Dirk


-- 
https://www.themobilepresenter.com/



From websitemaster at cogeco.net  Thu Nov 12 10:14:57 2015
From: websitemaster at cogeco.net (Tom)
Date: Thu, 12 Nov 2015 10:14:57 -0500
Subject: [geeklog-devel] Geeklog Demo Mode
Message-ID: <012201d11d5c$e4789700$ad69c500$@cogeco.net>

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




From niemans at nlbox.com  Thu Nov 12 12:03:22 2015
From: niemans at nlbox.com (Wim Niemans)
Date: Thu, 12 Nov 2015 18:03:22 +0100
Subject: [geeklog-devel] Geeklog Demo Mode
In-Reply-To: <012201d11d5c$e4789700$ad69c500$@cogeco.net>
References: <012201d11d5c$e4789700$ad69c500$@cogeco.net>
Message-ID: <C1184769-483A-4E8A-940D-1ACD30FEA9B0@nlbox.com>

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
> 



From ironmax at spacequad.com  Fri Nov 13 10:55:36 2015
From: ironmax at spacequad.com (Michael Brusletten)
Date: Fri, 13 Nov 2015 10:55:36 -0500
Subject: [geeklog-devel] geeklog-devel Digest, Vol 110, Issue 4
In-Reply-To: <mailman.1.1447396378.7019.geeklog-devel@lists.geeklog.net>
References: <mailman.1.1447396378.7019.geeklog-devel@lists.geeklog.net>
Message-ID: <FC949E2510B54C93A048FA14BB3F8F98@spacequad.com>

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
********************************************* 



From websitemaster at cogeco.net  Tue Nov 24 11:07:56 2015
From: websitemaster at cogeco.net (Tom)
Date: Tue, 24 Nov 2015 11:07:56 -0500
Subject: [geeklog-devel] Geeklog.net and Google
Message-ID: <021101d126d2$481d4340$d857c9c0$@cogeco.net>

Does anyone else have problems searching for Geeklog on Google? It seems to
be working fine for me but a few users have reported problems with access
denied errors:

https://www.geeklog.net/forum/viewtopic.php?msg=1&showtopic=96157&lastpost=t
rue#96160

Tom

-----Original Message-----
From: geeklog-devel [mailto:geeklog-devel-bounces at lists.geeklog.net] On
Behalf Of Tom
Sent: Thursday, November 12, 2015 10:15 AM
To: 'Geeklog Development' <geeklog-devel at lists.geeklog.net>
Subject: [geeklog-devel] Geeklog Demo Mode

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



From dirk at haun-online.de  Tue Nov 24 11:18:57 2015
From: dirk at haun-online.de (Dirk Haun)
Date: Tue, 24 Nov 2015 17:18:57 +0100
Subject: [geeklog-devel] Geeklog.net and Google
In-Reply-To: <021101d126d2$481d4340$d857c9c0$@cogeco.net>
References: <021101d126d2$481d4340$d857c9c0$@cogeco.net>
Message-ID: <F59709A6-2E18-4968-BA54-515B2D2F17E9@haun-online.de>

Tom <websitemaster at cogeco.net> wrote:

> Does anyone else have problems searching for Geeklog on Google? It seems to
> be working fine for me but a few users have reported problems with access
> denied errors:

My guess is that it's a case of overzealous spam blocking in the .htaccess. I don't think we block any Google IP addresses (at least I would hope so), but we may block access to some unusual user agents or requests.

Having the exact date and time when it happened would help, to check the log files.

Dirk


-- 
https://www.themobilepresenter.com/



From websitemaster at cogeco.net  Tue Nov 24 14:21:10 2015
From: websitemaster at cogeco.net (Tom)
Date: Tue, 24 Nov 2015 14:21:10 -0500
Subject: [geeklog-devel] Geeklog.net and Google
In-Reply-To: <F59709A6-2E18-4968-BA54-515B2D2F17E9@haun-online.de>
References: <021101d126d2$481d4340$d857c9c0$@cogeco.net>
 <F59709A6-2E18-4968-BA54-515B2D2F17E9@haun-online.de>
Message-ID: <022601d126ed$470ca250$d525e6f0$@cogeco.net>

Hmm wouldn't they always be blocked then? They can access the site, just not
by clicking on a link from Google Search.

Tom

-----Original Message-----
From: geeklog-devel [mailto:geeklog-devel-bounces at lists.geeklog.net] On
Behalf Of Dirk Haun
Sent: Tuesday, November 24, 2015 11:19 AM
To: Geeklog Development <geeklog-devel at lists.geeklog.net>
Subject: Re: [geeklog-devel] Geeklog.net and Google

Tom <websitemaster at cogeco.net> wrote:

> Does anyone else have problems searching for Geeklog on Google? It 
> seems to be working fine for me but a few users have reported problems 
> with access denied errors:

My guess is that it's a case of overzealous spam blocking in the .htaccess.
I don't think we block any Google IP addresses (at least I would hope so),
but we may block access to some unusual user agents or requests.

Having the exact date and time when it happened would help, to check the log
files.

Dirk


--
https://www.themobilepresenter.com/

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



From websitemaster at cogeco.net  Wed Nov 25 09:34:31 2015
From: websitemaster at cogeco.net (Tom)
Date: Wed, 25 Nov 2015 09:34:31 -0500
Subject: [geeklog-devel] Geeklog.net and Google and next release
Message-ID: <001301d1278e$6619ef30$324dcd90$@cogeco.net>

Okay, I have posted on the forum about providing more information.

I also notice that I am not getting any forum email notifications anymore
about new posts.  I will have to look into this to see if this is either a
forum issue or Geeklog issue. Because of this I doubt I will do the final
Geeklog 2.1.1 release this week. It will probably be pushed to next week.

Tom

-----Original Message-----
From: geeklog-devel [mailto:geeklog-devel-bounces at lists.geeklog.net] On
Behalf Of Tom
Sent: Tuesday, November 24, 2015 2:21 PM
To: 'Geeklog Development' <geeklog-devel at lists.geeklog.net>
Subject: Re: [geeklog-devel] Geeklog.net and Google

Hmm wouldn't they always be blocked then? They can access the site, just not
by clicking on a link from Google Search.

Tom

-----Original Message-----
From: geeklog-devel [mailto:geeklog-devel-bounces at lists.geeklog.net] On
Behalf Of Dirk Haun
Sent: Tuesday, November 24, 2015 11:19 AM
To: Geeklog Development <geeklog-devel at lists.geeklog.net>
Subject: Re: [geeklog-devel] Geeklog.net and Google

Tom <websitemaster at cogeco.net> wrote:

> Does anyone else have problems searching for Geeklog on Google? It 
> seems to be working fine for me but a few users have reported problems 
> with access denied errors:

My guess is that it's a case of overzealous spam blocking in the .htaccess.
I don't think we block any Google IP addresses (at least I would hope so),
but we may block access to some unusual user agents or requests.

Having the exact date and time when it happened would help, to check the log
files.

Dirk


--
https://www.themobilepresenter.com/

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

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



From websitemaster at cogeco.net  Thu Nov 26 15:14:21 2015
From: websitemaster at cogeco.net (Tom)
Date: Thu, 26 Nov 2015 15:14:21 -0500
Subject: [geeklog-devel] Geeklog.net and Forum Notifications
Message-ID: <008301d12887$095cfcc0$1c16f640$@cogeco.net>

Okay so the bug was in the forum notifications and not Geeklog. Basically if
you created or replied to a topic and set the notification it wouldn't work
and the notification record would not be created in the database.

It was an easy fix (value needed to be 1 and not 'on') and I updated
createtopic.php on Geeklog.net with it. The forum repository also has been
updated.  I guess I will have to release forum 2.9.3 with the new fix.

Tom