From cordiste at free.fr Mon Oct 7 10:22:29 2013 From: cordiste at free.fr (cordiste) Date: Mon, 7 Oct 2013 16:22:29 +0200 Subject: [geeklog-devel] Registering My Favorite WYSIWYG HTML Editor In-Reply-To: References: <76e0b45d296c.520e8a38@cgocable.ca> <7770e88f458e.520e8a75@cgocable.ca> <7720ca46226.520e8ab4@cgocable.ca> <7720803124af.520e8af1@cgocable.ca> <7740f73537c5.520e8b2e@cgocable.ca> <77e0c9453723.520e8b6f@cgocable.ca> <76e0ee986ef3.520e8bae@cgocable.ca> <7770ef722940.520e8bed@cgocable.ca> <7710ea906cdb.520e8c2c@cgocable.ca> <7790a79c820.520e8c6a@cgocable.ca> <7790d16c4cdf.520e5464@cgocable.ca> <7440a36a10d3e.520e95d3@cgocable.ca> <75e0a49d11c3c.520e9612@cgocable.ca> <7460bf031376c.520e9650@cgocable.ca> <76a09d1e16b4c.520e5e13@cgocable.ca> Message-ID: Did someone ever try xhEditor [1] ? xhEditor is a simple,small,fast WYSWYG(What You See What You Get) XHTML editor based on jQuery and compatible with Internet Explorer 6.0+,Firefox 3.0+,Opera 9.6+,Chrome 1.0+,Safari 3.22+ Ben [1] http://xheditor.com/demo 2013/8/17 Yoshinori Tahara : > Tom wrote: >> I like solution 2 better as well. This way Geeklog has full control of the >> editor selected and you can have more than one editor installed. Doing it >> the other way may create problems if you have 2 plugins installed that each >> have a different editor. > > Thanks for your agreement. > But I think even in the case of Solution 1, to be able to manage more than > one editor without problems. > > > Tom wrote: >> My one question is do we want the user to be able to select their own >> advance editor if more than one is installed? I personally would say no. I >> would want them to only use the one I have selected for the site. > > I agree with your opinion. > However, we should allow the user to be able to select their own editor like > that the user can select their own theme. > It is up to the site administrator to give the right of choice to the user. > > Tom wrote: >> The only other downside to me is that plugins are easy to install since >> you can do it from the Geeklog plugin interface. At some point in the future >> we should try to add an interface so webmasters can install themes and >> editors directly from the Geeklog Admin. > > I agree with your opinion. > > > > Wim wrote: >> Agree with Tom, with one exception. >> >> I agree that is not up to the user to select a specific editor. But it is >> up the role the user is playing. >> Comment posting could do entirely with the most basic editor available. >> See what I mean at LinkedIn: they are using a fine feature for posting >> comments; no decorations, only user experience. >> Than I guess a story admin, aka CMS user, would like to use the most >> advanced editor available for drafting new stories. > > I appreciate your opinion. > I also think I want to enable the selection of the feature of the editor for > the posting comments. > > > -- > Yoshinori Tahara - dengen > > > _______________________________________________ > geeklog-devel mailing list > geeklog-devel at lists.geeklog.net > http://eight.pairlist.net/mailman/listinfo/geeklog-devel > From hamon.erwan at free.fr Mon Oct 7 15:49:51 2013 From: hamon.erwan at free.fr (Erwan HAMON) Date: Mon, 7 Oct 2013 21:49:51 +0200 Subject: [geeklog-devel] Doing a Geeklog upgrade Message-ID: <201310072149.51912.hamon.erwan@free.fr> Hi all, I am working at upgrading a website based on a fairly old Geeklog release that has been patched and customised by various people over the years. After making good progress on hacking a CLI upgrade process to get it up to Geeklog 2.0.0, I decided I needed to find out what is the best channel to discuss with the Geeklog project. There are bugs which I've found and fixed, custom features in place or required that could be shared with upstream Geeklog. It looks like this is the best list to join. Isn't it ? Regards, -- Erwan HAMON - http://hamon.erwan.free.fr/ -------------- next part -------------- An HTML attachment was scrubbed... URL: From websitemaster at cogeco.net Mon Oct 7 17:19:01 2013 From: websitemaster at cogeco.net (Tom) Date: Mon, 7 Oct 2013 17:19:01 -0400 Subject: [geeklog-devel] Registering My Favorite WYSIWYG HTML Editor In-Reply-To: References: <76e0b45d296c.520e8a38@cgocable.ca> <7770e88f458e.520e8a75@cgocable.ca> <7720ca46226.520e8ab4@cgocable.ca> <7720803124af.520e8af1@cgocable.ca> <7740f73537c5.520e8b2e@cgocable.ca> <77e0c9453723.520e8b6f@cgocable.ca> <76e0ee986ef3.520e8bae@cgocable.ca> <7770ef722940.520e8bed@cgocable.ca> <7710ea906cdb.520e8c2c@cgocable.ca> <7790a79c820.520e8c6a@cgocable.ca> <7790d16c4cdf.520e5464@cgocable.ca> <7440a36a10d3e.520e95d3@cgocable.ca> <75e0a49d11c3c.520e9612@cgocable.ca> <7460bf031376c.520e9650@cgocable.ca> <76a09d1e16b4c.520e5e13@cgocable.ca> Message-ID: <00e901cec3a2$d8423920$88c6ab60$@cogeco.net> I haven't tried that one before. Currently Geeklog 2.1.0 has the FCK and the CK editor bundled with it. Dengen also made it much easier to add additional editors which is now selectable in the Geeklog Config. Tom -----Original Message----- From: geeklog-devel-bounces at lists.geeklog.net [mailto:geeklog-devel-bounces at lists.geeklog.net] On Behalf Of cordiste Sent: October-07-13 10:22 AM To: Geeklog Development Subject: Re: [geeklog-devel] Registering My Favorite WYSIWYG HTML Editor Did someone ever try xhEditor [1] ? xhEditor is a simple,small,fast WYSWYG(What You See What You Get) XHTML editor based on jQuery and compatible with Internet Explorer 6.0+,Firefox 3.0+,Opera 9.6+,Chrome 1.0+,Safari 3.22+ Ben [1] http://xheditor.com/demo 2013/8/17 Yoshinori Tahara : > Tom wrote: >> I like solution 2 better as well. This way Geeklog has full control >> of the editor selected and you can have more than one editor >> installed. Doing it the other way may create problems if you have 2 >> plugins installed that each have a different editor. > > Thanks for your agreement. > But I think even in the case of Solution 1, to be able to manage more > than one editor without problems. > > > Tom wrote: >> My one question is do we want the user to be able to select their own >> advance editor if more than one is installed? I personally would say >> no. I would want them to only use the one I have selected for the site. > > I agree with your opinion. > However, we should allow the user to be able to select their own > editor like that the user can select their own theme. > It is up to the site administrator to give the right of choice to the user. > > Tom wrote: >> The only other downside to me is that plugins are easy to install >> since you can do it from the Geeklog plugin interface. At some point >> in the future we should try to add an interface so webmasters can >> install themes and editors directly from the Geeklog Admin. > > I agree with your opinion. > > > > Wim wrote: >> Agree with Tom, with one exception. >> >> I agree that is not up to the user to select a specific editor. But >> it is up the role the user is playing. >> Comment posting could do entirely with the most basic editor available. >> See what I mean at LinkedIn: they are using a fine feature for >> posting comments; no decorations, only user experience. >> Than I guess a story admin, aka CMS user, would like to use the most >> advanced editor available for drafting new stories. > > I appreciate your opinion. > I also think I want to enable the selection of the feature of the > editor for the posting comments. > > > -- > Yoshinori Tahara - dengen > > > _______________________________________________ > geeklog-devel mailing list > geeklog-devel at lists.geeklog.net > http://eight.pairlist.net/mailman/listinfo/geeklog-devel > _______________________________________________ geeklog-devel mailing list geeklog-devel at lists.geeklog.net http://eight.pairlist.net/mailman/listinfo/geeklog-devel From websitemaster at cogeco.net Mon Oct 7 17:23:39 2013 From: websitemaster at cogeco.net (Tom) Date: Mon, 7 Oct 2013 17:23:39 -0400 Subject: [geeklog-devel] Doing a Geeklog upgrade In-Reply-To: <201310072149.51912.hamon.erwan@free.fr> References: <201310072149.51912.hamon.erwan@free.fr> Message-ID: <00ea01cec3a3$7dc10390$79430ab0$@cogeco.net> This would be the place J We hope to release Geeklog 2.1.0 in the next month or so (beta) which fixes a number of bugs and adds a number of new features. The latest code base is here: http://www.geeklog.net/staticpages/index.php/CVS You can check out and add bug report and feature requests here: http://project.geeklog.net/ and your more than welcome to discuss any bugs, features patches you may have on this mailing list. Tom From: geeklog-devel-bounces at lists.geeklog.net [mailto:geeklog-devel-bounces at lists.geeklog.net] On Behalf Of Erwan HAMON Sent: October-07-13 3:50 PM To: geeklog-devel at lists.geeklog.net Subject: [geeklog-devel] Doing a Geeklog upgrade Hi all, I am working at upgrading a website based on a fairly old Geeklog release that has been patched and customised by various people over the years. After making good progress on hacking a CLI upgrade process to get it up to Geeklog 2.0.0, I decided I needed to find out what is the best channel to discuss with the Geeklog project. There are bugs which I've found and fixed, custom features in place or required that could be shared with upstream Geeklog. It looks like this is the best list to join. Isn't it ? Regards, -- Erwan HAMON - http://hamon.erwan.free.fr/ -------------- next part -------------- An HTML attachment was scrubbed... URL: From danstoner at gmail.com Mon Oct 7 17:01:36 2013 From: danstoner at gmail.com (Dan Stoner) Date: Mon, 7 Oct 2013 17:01:36 -0400 Subject: [geeklog-devel] Doing a Geeklog upgrade In-Reply-To: <201310072149.51912.hamon.erwan@free.fr> References: <201310072149.51912.hamon.erwan@free.fr> Message-ID: Welcome! Yes, I think you have found the best place to participate and reach the developers. - Dan Stoner On Oct 7, 2013 3:50 PM, "Erwan HAMON" wrote: > ** > > Hi all, > > > > I am working at upgrading a website based on a fairly old Geeklog > > release that has been patched and customised by various people over the > > years. > > > > After making good progress on hacking a CLI upgrade process to get it up > > to Geeklog 2.0.0, I decided I needed to find out what is the best > > channel to discuss with the Geeklog project. There are bugs which I've > > found and fixed, custom features in place or required that could be > > shared with upstream Geeklog. > > > > It looks like this is the best list to join. Isn't it ? > > > > Regards, > > > > -- > > Erwan HAMON - http://hamon.erwan.free.fr/ > > > > _______________________________________________ > geeklog-devel mailing list > geeklog-devel at lists.geeklog.net > http://eight.pairlist.net/mailman/listinfo/geeklog-devel > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From dirk at haun-online.de Tue Oct 8 03:46:55 2013 From: dirk at haun-online.de (Dirk Haun) Date: Tue, 08 Oct 2013 09:46:55 +0200 Subject: [geeklog-devel] Doing a Geeklog upgrade In-Reply-To: <201310072149.51912.hamon.erwan@free.fr> References: <201310072149.51912.hamon.erwan@free.fr> Message-ID: <20131008094655.Horde.ZbsKMpbwVS3BG9X8MlRMZA1@webmail.df.eu> Quoting Erwan HAMON : > There are bugs which I've > found and fixed, custom features in place or required that could be > shared with upstream Geeklog. As Tom already wrote: If you found bugs, please check if they still exist in the current development version. If so, open bug reports or send patches if you already fixed them. Thanks! You can get the development version from our Mercurial repository or as a tarball, ready for installation: http://wiki.geeklog.net/index.php/Nightly_Tarball As for the customisations: Geeklog has a lot of hooks that let you add customisations without having to modify the core code. Specifically, you could write a plugin or you use the CUSTOM_ hooks. It's probably best if you tell us what you customised, so that we can suggest ways to implement this in a more future-proof way. Depending on the feature, we may want to introduce new hooks or maybe even pick one of your customisations up and make it a standard feature :) Writing a plugin isn't as scary as it may sound, btw. Start here: http://wiki.geeklog.net/index.php/Minimal_Plugin bye, Dirk -- http://www.themobilepresenter.com/ From hamon.erwan at free.fr Tue Oct 8 16:29:42 2013 From: hamon.erwan at free.fr (Erwan HAMON) Date: Tue, 8 Oct 2013 22:29:42 +0200 Subject: [geeklog-devel] Geeklog-Nightly fail to install Message-ID: <201310082229.43783.hamon.erwan@free.fr> Hi, I've created myself an account on Mantis but cannot report bugs against 2.1.0 or nightly. Here is a wicked bug and a patch. Geeklog-Nightly Build #524 (Oct 1, 2013 8:02:22 AM) fails to install and only leaves this message in the error.log: Thu Oct 3 07:23:50 2013 - ::1 - 2 - file_put_contents(instance__topic_tree__c81e728d9d4c2f636f067f89cc14862c.php): failed to open stream: Permission denied @ /path/to/geeklog-nightly/system/classes/template.class.php line 2091 It took me a while to find out it's because lib-common, hence template.class.php, is included from within a function. $TEMPLATE_OPTIONS is initialised as a local variable within that function's scope. The global $TEMPLATE_OPTIONS remains null. Bellow is a patch that allows the install to get thru, but it might be better to review $TEMPLATE_OPTIONS' initialisation or to forbid includes from within a function: --- /path/to/vanilla/geeklog-nightly/public_html/lib-common.php 2013-10-01 14:03:12.000000000 +0200 +++ /path/to/my/geeklog-nightly/public_html/lib-common.php 2013-10-08 19:01:01.652876627 +0200 @@ -527,7 +527,9 @@ $_TOPICS = TOPIC_buildTree(TOPIC_ROOT, true); // Save updated topic tree and date - CACHE_create_instance($cacheInstance, serialize($_TOPICS), true); + if (isset($GLOBALS['TEMPLATE_OPTIONS']) && is_array($TEMPLATE_OPTIONS) && isset($TEMPLATE_OPTIONS['path_cache'])) { + CACHE_create_instance($cacheInstance, serialize($_TOPICS), true); + } } else { $_TOPICS = unserialize($serialized_topic_tree); } -- Erwan HAMON - http://hamon.erwan.free.fr/ From hamon.erwan at free.fr Tue Oct 8 16:55:49 2013 From: hamon.erwan at free.fr (Erwan HAMON) Date: Tue, 8 Oct 2013 22:55:49 +0200 Subject: [geeklog-devel] Doing a Geeklog upgrade In-Reply-To: <00ea01cec3a3$7dc10390$79430ab0$@cogeco.net> References: <201310072149.51912.hamon.erwan@free.fr> <00ea01cec3a3$7dc10390$79430ab0$@cogeco.net> Message-ID: <201310082255.49884.hamon.erwan@free.fr> Le lundi 7 octobre 2013 23:23, Tom a ?crit : >You can check out and add bug report and feature requests here: > >http://project.geeklog.net/ > >and your more than welcome to discuss any bugs, features patches you >may have on this mailing list. OK, Now that I have nightly working, I'll review all my patches against the latest code base. (At least the 1.1.3 MySQL upgrade in plugins/calendar seems to already have been fixed). Regards, -- Erwan HAMON - http://hamon.erwan.free.fr/ From websitemaster at cogeco.net Tue Oct 8 19:11:36 2013 From: websitemaster at cogeco.net (Tom) Date: Tue, 8 Oct 2013 19:11:36 -0400 Subject: [geeklog-devel] Geeklog-Nightly fail to install In-Reply-To: <201310082229.43783.hamon.erwan@free.fr> References: <201310082229.43783.hamon.erwan@free.fr> Message-ID: <015f01cec47b$bce6d8f0$36b48ad0$@cogeco.net> Thanks for the bug report. I have added it in http://project.geeklog.net/tracking/view.php?id=1702 Let's see what Dirks says about you (and I am assuming other normal users) not being able to add in a bug report for 2.1.0. I don't see why you shouldn't be allowed to (or any version currently in development). I will have to take a look at this bug. I haven't done a complete install in a while and only upgrades recently. Yeah $TEMPLATE_OPTIONS had to be coded that way to remain compatible. The layout path probably hasn't been set or loaded yet hence the error so your solution is probably the best one but I will run the install a few times when I have time to check it out. Tom -----Original Message----- From: geeklog-devel-bounces at lists.geeklog.net [mailto:geeklog-devel-bounces at lists.geeklog.net] On Behalf Of Erwan HAMON Sent: October-08-13 4:30 PM To: geeklog-devel at lists.geeklog.net Subject: [geeklog-devel] Geeklog-Nightly fail to install Hi, I've created myself an account on Mantis but cannot report bugs against 2.1.0 or nightly. Here is a wicked bug and a patch. Geeklog-Nightly Build #524 (Oct 1, 2013 8:02:22 AM) fails to install and only leaves this message in the error.log: Thu Oct 3 07:23:50 2013 - ::1 - 2 - file_put_contents(instance__topic_tree__c81e728d9d4c2f636f067f89cc14862c.php ): failed to open stream: Permission denied @ /path/to/geeklog-nightly/system/classes/template.class.php line 2091 It took me a while to find out it's because lib-common, hence template.class.php, is included from within a function. $TEMPLATE_OPTIONS is initialised as a local variable within that function's scope. The global $TEMPLATE_OPTIONS remains null. Bellow is a patch that allows the install to get thru, but it might be better to review $TEMPLATE_OPTIONS' initialisation or to forbid includes from within a function: --- /path/to/vanilla/geeklog-nightly/public_html/lib-common.php 2013-10-01 14:03:12.000000000 +0200 +++ /path/to/my/geeklog-nightly/public_html/lib-common.php 2013-10-08 19:01:01.652876627 +0200 @@ -527,7 +527,9 @@ $_TOPICS = TOPIC_buildTree(TOPIC_ROOT, true); // Save updated topic tree and date - CACHE_create_instance($cacheInstance, serialize($_TOPICS), true); + if (isset($GLOBALS['TEMPLATE_OPTIONS']) && is_array($TEMPLATE_OPTIONS) && isset($TEMPLATE_OPTIONS['path_cache'])) { + CACHE_create_instance($cacheInstance, serialize($_TOPICS), true); + } } else { $_TOPICS = unserialize($serialized_topic_tree); } -- Erwan HAMON - http://hamon.erwan.free.fr/ _______________________________________________ geeklog-devel mailing list geeklog-devel at lists.geeklog.net http://eight.pairlist.net/mailman/listinfo/geeklog-devel From dirk at haun-online.de Wed Oct 9 04:06:04 2013 From: dirk at haun-online.de (Dirk Haun) Date: Wed, 09 Oct 2013 10:06:04 +0200 Subject: [geeklog-devel] Geeklog-Nightly fail to install In-Reply-To: <015f01cec47b$bce6d8f0$36b48ad0$@cogeco.net> References: <201310082229.43783.hamon.erwan@free.fr> <015f01cec47b$bce6d8f0$36b48ad0$@cogeco.net> Message-ID: <20131009100604.Horde.zuPeXNiBZYNcTN_DoH2kuQ8@webmail.df.eu> Quoting Tom : > Let's see what Dirks says about you (and I am assuming other normal users) > not being able to add in a bug report for 2.1.0. I don't see why you > shouldn't be allowed to (or any version currently in development). Looks like versions that aren't released yet don't show up in the list for normal users. In that case, please pick some other version and leave a comment. I'd rather have a bug report for the wrong version than no bug report at all :) Thanks. The better option, I guess, would be to offer an ongoing "development version" entry. Any better ideas for the name? bye, Dirk -- http://www.themobilepresenter.com/ From websitemaster at cogeco.net Wed Oct 9 06:11:36 2013 From: websitemaster at cogeco.net (Tom) Date: Wed, 9 Oct 2013 06:11:36 -0400 Subject: [geeklog-devel] Geeklog-Nightly fail to install In-Reply-To: <20131009100604.Horde.zuPeXNiBZYNcTN_DoH2kuQ8@webmail.df.eu> References: <201310082229.43783.hamon.erwan@free.fr> <015f01cec47b$bce6d8f0$36b48ad0$@cogeco.net> <20131009100604.Horde.zuPeXNiBZYNcTN_DoH2kuQ8@webmail.df.eu> Message-ID: <018b01cec4d7$efd77290$cf8657b0$@cogeco.net> Hmm having "development" is better than reporting it under actual released versions IMO. Sort of how we use "Future" for features. Will this become an issue after several release cycles though? I found this link on the Mantis site (http://www.mantisbt.org/forums/viewtopic.php?f=3&t=21294) that shows how to allow all users to report bugs on unreleased versions. Is there a reason we would not want to do this? The default setting is that only developers and above are able to report to unreleased versions. Seems that all your versions are not set to released. You can set them to released or allow also reporters to report issues for unreleased versions. To change this add the following line to file config_inc.php Code: Select all$g_report_issues_for_unreleased_versions_threshold = REPORTER; Tom -----Original Message----- From: geeklog-devel-bounces at lists.geeklog.net [mailto:geeklog-devel-bounces at lists.geeklog.net] On Behalf Of Dirk Haun Sent: October-09-13 4:06 AM To: Geeklog Development Subject: Re: [geeklog-devel] Geeklog-Nightly fail to install Quoting Tom : > Let's see what Dirks says about you (and I am assuming other normal > users) not being able to add in a bug report for 2.1.0. I don't see > why you shouldn't be allowed to (or any version currently in development). Looks like versions that aren't released yet don't show up in the list for normal users. In that case, please pick some other version and leave a comment. I'd rather have a bug report for the wrong version than no bug report at all :) Thanks. The better option, I guess, would be to offer an ongoing "development version" entry. Any better ideas for the name? bye, Dirk -- http://www.themobilepresenter.com/ _______________________________________________ geeklog-devel mailing list geeklog-devel at lists.geeklog.net http://eight.pairlist.net/mailman/listinfo/geeklog-devel From dirk at haun-online.de Wed Oct 9 06:25:16 2013 From: dirk at haun-online.de (Dirk Haun) Date: Wed, 09 Oct 2013 12:25:16 +0200 Subject: [geeklog-devel] Geeklog-Nightly fail to install In-Reply-To: <018b01cec4d7$efd77290$cf8657b0$@cogeco.net> References: <201310082229.43783.hamon.erwan@free.fr> <015f01cec47b$bce6d8f0$36b48ad0$@cogeco.net> <20131009100604.Horde.zuPeXNiBZYNcTN_DoH2kuQ8@webmail.df.eu> <018b01cec4d7$efd77290$cf8657b0$@cogeco.net> Message-ID: <20131009122516.Horde.ovltZjHYydovMdkQhNJHCQ6@webmail.df.eu> Quoting Tom : > I found this link on the Mantis site > (http://www.mantisbt.org/forums/viewtopic.php?f=3&t=21294) that shows how to > allow all users to report bugs on unreleased versions. Is there a reason we > would not want to do this? Good find. I've activated this now and tested that it works. Goes to show what you're missing when always using your site in admin mode :) Applies to Geeklog, too, btw. bye, Dirk -- http://www.themobilepresenter.com/ From hiroron at hiroron.com Thu Oct 10 01:27:57 2013 From: hiroron at hiroron.com (hiroron) Date: Thu, 10 Oct 2013 14:27:57 +0900 Subject: [geeklog-devel] Registering My Favorite WYSIWYG HTML Editor In-Reply-To: References: <76e0b45d296c.520e8a38@cgocable.ca> <7770e88f458e.520e8a75@cgocable.ca> <7720ca46226.520e8ab4@cgocable.ca> <7720803124af.520e8af1@cgocable.ca> <7740f73537c5.520e8b2e@cgocable.ca> <77e0c9453723.520e8b6f@cgocable.ca> <76e0ee986ef3.520e8bae@cgocable.ca> <7770ef722940.520e8bed@cgocable.ca> <7710ea906cdb.520e8c2c@cgocable.ca> <7790a79c820.520e8c6a@cgocable.ca> <7790d16c4cdf.520e5464@cgocable.ca> <7440a36a10d3e.520e95d3@cgocable.ca> <75e0a49d11c3c.520e9612@cgocable.ca> <7460bf031376c.520e9650@cgocable.ca> <76a09d1e16b4c.520e5e13@cgocable.ca> Message-ID: <52563ADD.20000@hiroron.com> is not ever used the xheditor. I tried using in the demo site, but it sounds good! Hiroron (2013/10/07 23:22), cordiste wrote: > Did someone ever try xhEditor [1] ? > > xhEditor is a simple,small,fast WYSWYG(What You See What You Get) > XHTML editor based on jQuery and compatible with Internet Explorer > 6.0+,Firefox 3.0+,Opera 9.6+,Chrome 1.0+,Safari 3.22+ > > Ben > > [1] http://xheditor.com/demo > > > 2013/8/17 Yoshinori Tahara : >> Tom wrote: >>> I like solution 2 better as well. This way Geeklog has full control of the >>> editor selected and you can have more than one editor installed. Doing it >>> the other way may create problems if you have 2 plugins installed that each >>> have a different editor. >> >> Thanks for your agreement. >> But I think even in the case of Solution 1, to be able to manage more than >> one editor without problems. >> >> >> Tom wrote: >>> My one question is do we want the user to be able to select their own >>> advance editor if more than one is installed? I personally would say no. I >>> would want them to only use the one I have selected for the site. >> >> I agree with your opinion. >> However, we should allow the user to be able to select their own editor like >> that the user can select their own theme. >> It is up to the site administrator to give the right of choice to the user. >> >> Tom wrote: >>> The only other downside to me is that plugins are easy to install since >>> you can do it from the Geeklog plugin interface. At some point in the future >>> we should try to add an interface so webmasters can install themes and >>> editors directly from the Geeklog Admin. >> >> I agree with your opinion. >> >> >> >> Wim wrote: >>> Agree with Tom, with one exception. >>> >>> I agree that is not up to the user to select a specific editor. But it is >>> up the role the user is playing. >>> Comment posting could do entirely with the most basic editor available. >>> See what I mean at LinkedIn: they are using a fine feature for posting >>> comments; no decorations, only user experience. >>> Than I guess a story admin, aka CMS user, would like to use the most >>> advanced editor available for drafting new stories. >> >> I appreciate your opinion. >> I also think I want to enable the selection of the feature of the editor for >> the posting comments. >> >> >> -- >> Yoshinori Tahara - dengen >> >> >> _______________________________________________ >> geeklog-devel mailing list >> geeklog-devel at lists.geeklog.net >> http://eight.pairlist.net/mailman/listinfo/geeklog-devel >> > _______________________________________________ > geeklog-devel mailing list > geeklog-devel at lists.geeklog.net > http://eight.pairlist.net/mailman/listinfo/geeklog-devel > From dirk at haun-online.de Sat Oct 12 16:47:11 2013 From: dirk at haun-online.de (Dirk Haun) Date: Sat, 12 Oct 2013 22:47:11 +0200 Subject: [geeklog-devel] Reducing the number of HTTP requests Message-ID: <58A0B7C9-8DDD-4069-B46E-5A5FEB56FE63@haun-online.de> While hunting down some profile spammers, I noticed (not for the first time) that it does take quite a lot of HTTP requests to load the Geeklog homepage. Below is a list of what it takes to load and display our homepage. These are real numbers, grep'ed from the web server log file just now. First column is a timestamp, followed by the URL and the number of bytes sent. That's 34 HTTP requests. Note that it takes a full six seconds to send everything (1 second to render the page, then 5 seconds until the last resource has been requested). That's not exactly a great response time, to put it mildly. This will get better on subsequent pages, when the browser caches things. But 6 seconds is what it takes for a first-time visitor. (The visitor came from a DSL line and the server wasn't busy at the time) I see a few obvious things (why are we loading the CSS for polls and captcha on the front page?) and a few potential fixes (merge JavaScript files; maybe also some of the images). Other ideas? bye, Dirk --- snip --- 16:20:43 / (11012) 16:20:44 /layout/modern_curve/style.css.php?dir=ltr (59466) 16:20:45 /polls/style.css (1538) 16:20:45 /captcha/style.css (684) 16:20:45 /forum/forum/layout/forum.css (3256) 16:20:45 /layout/modern_curve/images/logo.png (16336) 16:20:45 /javascript/common.js (4244) 16:20:45 /forum/smilies.css.php (1828) 16:20:45 /javascript/jquery.min.js (92923) 16:20:45 /layout/modern_curve/javascript/fix_html.js (1435) 16:20:45 /layout/modern_curve/javascript/confirm.js (501) 16:20:46 /layout/modern_curve/javascript/search.js (1076) 16:20:47 /images/facebook-login-icon.png (845) 16:20:47 /images/twitter-login-icon.png (911) 16:20:47 /images/openid_login_icon.png (812) 16:20:47 /layout/modern_curve/images/print.png (756) 16:20:48 /images/topics/announcements.png (3847) 16:20:48 /images/topics/plugins.png (2717) 16:20:48 /images/buttons/download.png (6977) 16:20:48 /docs/images/de.png (694) 16:20:48 /docs/images/pl.png (631) 16:20:48 /docs/images/jp.png (641) 16:20:48 /docs/images/fr.png (675) 16:20:48 /docs/images/es.png (687) 16:20:48 /javascript/fix_tooltips.js (1596) 16:20:48 /javascript/login.js (1082) 16:20:48 /layout/modern_curve/images/css/bg.png (587) 16:20:48 /layout/modern_curve/images/css/bg_header.png (485) 16:20:48 /layout/modern_curve/images/css/menu_bg.png (466) 16:20:48 /layout/modern_curve/images/css/block_bg.png (577) 16:20:49 /layout/modern_curve/images/css/search-right.png (6671) 16:20:49 /images/buttons/feed.png (896) 16:20:49 /layout/modern_curve/images/button_help.png (532) 16:20:49 /layout/modern_curve/images/favicon.ico (1429) -- http://www.themobilepresenter.com/ From niemans at nlbox.com Sat Oct 12 17:38:07 2013 From: niemans at nlbox.com (Niemans) Date: Sat, 12 Oct 2013 23:38:07 +0200 Subject: [geeklog-devel] new version 2.10 - where? Message-ID: My plugin code and theme files must use the new text and template features. So, I would like to upgrade to 2.1.0. From where can that release be downloaded? Is there a change log, and is it already complete? Thanks, wim niemans ri From niemans at nlbox.com Sat Oct 12 17:34:16 2013 From: niemans at nlbox.com (Niemans) Date: Sat, 12 Oct 2013 23:34:16 +0200 Subject: [geeklog-devel] is using iframe wise? Message-ID: <188EB57F-6634-421C-A899-4D2A9D4E050D@nlbox.com> Hello all, to embed an application in a site driven by geeklog, I am considering using iframe to replace the center blocks. Not to embed bocks in there, but an application that takes a large part of the window. Within the iframe ajax will be used. Is this a bad idea, are security issues known when iframe is used? Is information available on do's and don't 's? Thought, help? Thanks in advance, wim niemans ri From dirk at haun-online.de Sat Oct 12 18:06:18 2013 From: dirk at haun-online.de (Dirk Haun) Date: Sun, 13 Oct 2013 00:06:18 +0200 Subject: [geeklog-devel] new version 2.10 - where? In-Reply-To: References: Message-ID: <24A55FDC-1045-43C6-95E3-CA7E853EAF0D@haun-online.de> Niemans wrote: > So, I would like to upgrade to 2.1.0. From where can that release be downloaded? > Is there a change log, and is it already complete? Geeklog 2.1.0 hasn't been released yet. For a preview, you can download the nightly tar ball from http://wiki.geeklog.net/index.php/Nightly_Tarball A list of changes can be found here: http://project.geeklog.net/tracking/changelog_page.php bye, Dirk -- http://www.themobilepresenter.com/ From danstoner at gmail.com Sat Oct 12 18:18:53 2013 From: danstoner at gmail.com (Dan Stoner) Date: Sat, 12 Oct 2013 18:18:53 -0400 Subject: [geeklog-devel] is using iframe wise? In-Reply-To: <188EB57F-6634-421C-A899-4D2A9D4E050D@nlbox.com> References: <188EB57F-6634-421C-A899-4D2A9D4E050D@nlbox.com> Message-ID: Google for iframes are evil Iframes are bad ... - Dan Stoner On Oct 12, 2013 5:57 PM, "Niemans" wrote: > Hello all, > > to embed an application in a site driven by geeklog, I am considering > using iframe to replace the center blocks. > Not to embed bocks in there, but an application that takes a large part of > the window. Within the iframe ajax will be used. > > Is this a bad idea, are security issues known when iframe is used? > Is information available on do's and don't 's? > > Thought, help? > > Thanks in advance, > wim niemans ri > > _______________________________________________ > geeklog-devel mailing list > geeklog-devel at lists.geeklog.net > http://eight.pairlist.net/mailman/listinfo/geeklog-devel > -------------- next part -------------- An HTML attachment was scrubbed... URL: From websitemaster at cogeco.net Sat Oct 12 19:40:04 2013 From: websitemaster at cogeco.net (Tom) Date: Sat, 12 Oct 2013 19:40:04 -0400 Subject: [geeklog-devel] Reducing the number of HTTP requests In-Reply-To: <58A0B7C9-8DDD-4069-B46E-5A5FEB56FE63@haun-online.de> References: <58A0B7C9-8DDD-4069-B46E-5A5FEB56FE63@haun-online.de> Message-ID: <001801cec7a4$6056ac60$21040520$@cogeco.net> >> I see a few obvious things (why are we loading the CSS for polls and captcha on the front page?) Basically for the plugins to support Geeklog 1.8.2 and lower. As of Geeklog 2.0.0 since we generate the entire page at the end we can take into account if an autotag gets called and displays something that requires the css file. With Geeklog 1.8.2 and lower we cannot since the header is one of the first things generated. That being said I think the latest version of the polls plugin now requires Geeklog 2.0.0 so that could be switched. Tom -----Original Message----- From: geeklog-devel-bounces at lists.geeklog.net [mailto:geeklog-devel-bounces at lists.geeklog.net] On Behalf Of Dirk Haun Sent: October-12-13 4:47 PM To: geeklog-devel at lists.geeklog.net Subject: [geeklog-devel] Reducing the number of HTTP requests While hunting down some profile spammers, I noticed (not for the first time) that it does take quite a lot of HTTP requests to load the Geeklog homepage. Below is a list of what it takes to load and display our homepage. These are real numbers, grep'ed from the web server log file just now. First column is a timestamp, followed by the URL and the number of bytes sent. That's 34 HTTP requests. Note that it takes a full six seconds to send everything (1 second to render the page, then 5 seconds until the last resource has been requested). That's not exactly a great response time, to put it mildly. This will get better on subsequent pages, when the browser caches things. But 6 seconds is what it takes for a first-time visitor. (The visitor came from a DSL line and the server wasn't busy at the time) I see a few obvious things (why are we loading the CSS for polls and captcha on the front page?) and a few potential fixes (merge JavaScript files; maybe also some of the images). Other ideas? bye, Dirk --- snip --- 16:20:43 / (11012) 16:20:44 /layout/modern_curve/style.css.php?dir=ltr (59466) 16:20:45 /polls/style.css (1538) 16:20:45 /captcha/style.css (684) 16:20:45 /forum/forum/layout/forum.css (3256) 16:20:45 /layout/modern_curve/images/logo.png (16336) 16:20:45 /javascript/common.js (4244) 16:20:45 /forum/smilies.css.php (1828) 16:20:45 /javascript/jquery.min.js (92923) 16:20:45 /layout/modern_curve/javascript/fix_html.js (1435) 16:20:45 /layout/modern_curve/javascript/confirm.js (501) 16:20:46 /layout/modern_curve/javascript/search.js (1076) 16:20:47 /images/facebook-login-icon.png (845) 16:20:47 /images/twitter-login-icon.png (911) 16:20:47 /images/openid_login_icon.png (812) 16:20:47 /layout/modern_curve/images/print.png (756) 16:20:48 /images/topics/announcements.png (3847) 16:20:48 /images/topics/plugins.png (2717) 16:20:48 /images/buttons/download.png (6977) 16:20:48 /docs/images/de.png (694) 16:20:48 /docs/images/pl.png (631) 16:20:48 /docs/images/jp.png (641) 16:20:48 /docs/images/fr.png (675) 16:20:48 /docs/images/es.png (687) 16:20:48 /javascript/fix_tooltips.js (1596) 16:20:48 /javascript/login.js (1082) 16:20:48 /layout/modern_curve/images/css/bg.png (587) 16:20:48 /layout/modern_curve/images/css/bg_header.png (485) 16:20:48 /layout/modern_curve/images/css/menu_bg.png (466) 16:20:48 /layout/modern_curve/images/css/block_bg.png (577) 16:20:49 /layout/modern_curve/images/css/search-right.png (6671) 16:20:49 /images/buttons/feed.png (896) 16:20:49 /layout/modern_curve/images/button_help.png (532) 16:20:49 /layout/modern_curve/images/favicon.ico (1429) -- http://www.themobilepresenter.com/ _______________________________________________ geeklog-devel mailing list geeklog-devel at lists.geeklog.net http://eight.pairlist.net/mailman/listinfo/geeklog-devel From danstoner at gmail.com Sat Oct 12 19:40:50 2013 From: danstoner at gmail.com (Dan Stoner) Date: Sat, 12 Oct 2013 19:40:50 -0400 Subject: [geeklog-devel] Reducing the number of HTTP requests In-Reply-To: <58A0B7C9-8DDD-4069-B46E-5A5FEB56FE63@haun-online.de> References: <58A0B7C9-8DDD-4069-B46E-5A5FEB56FE63@haun-online.de> Message-ID: Can you reproduce using browser Web Developer tools? Chrome has a Net tab that times each request, gives size, etc. I have noticed Geeklog.net "feels" slow sometimes, I just assumed it was a figment of the hosting server. - Dan Stoner On Oct 12, 2013 4:47 PM, "Dirk Haun" wrote: > While hunting down some profile spammers, I noticed (not for the first > time) that it does take quite a lot of HTTP requests to load the Geeklog > homepage. > > Below is a list of what it takes to load and display our homepage. These > are real numbers, grep'ed from the web server log file just now. First > column is a timestamp, followed by the URL and the number of bytes sent. > > That's 34 HTTP requests. Note that it takes a full six seconds to send > everything (1 second to render the page, then 5 seconds until the last > resource has been requested). That's not exactly a great response time, to > put it mildly. This will get better on subsequent pages, when the browser > caches things. But 6 seconds is what it takes for a first-time visitor. > > (The visitor came from a DSL line and the server wasn't busy at the time) > > I see a few obvious things (why are we loading the CSS for polls and > captcha on the front page?) and a few potential fixes (merge JavaScript > files; maybe also some of the images). > > Other ideas? > > bye, Dirk > > > --- snip --- > 16:20:43 / (11012) > 16:20:44 /layout/modern_curve/style.css.php?dir=ltr (59466) > 16:20:45 /polls/style.css (1538) > 16:20:45 /captcha/style.css (684) > 16:20:45 /forum/forum/layout/forum.css (3256) > 16:20:45 /layout/modern_curve/images/logo.png (16336) > 16:20:45 /javascript/common.js (4244) > 16:20:45 /forum/smilies.css.php (1828) > 16:20:45 /javascript/jquery.min.js (92923) > 16:20:45 /layout/modern_curve/javascript/fix_html.js (1435) > 16:20:45 /layout/modern_curve/javascript/confirm.js (501) > 16:20:46 /layout/modern_curve/javascript/search.js (1076) > 16:20:47 /images/facebook-login-icon.png (845) > 16:20:47 /images/twitter-login-icon.png (911) > 16:20:47 /images/openid_login_icon.png (812) > 16:20:47 /layout/modern_curve/images/print.png (756) > 16:20:48 /images/topics/announcements.png (3847) > 16:20:48 /images/topics/plugins.png (2717) > 16:20:48 /images/buttons/download.png (6977) > 16:20:48 /docs/images/de.png (694) > 16:20:48 /docs/images/pl.png (631) > 16:20:48 /docs/images/jp.png (641) > 16:20:48 /docs/images/fr.png (675) > 16:20:48 /docs/images/es.png (687) > 16:20:48 /javascript/fix_tooltips.js (1596) > 16:20:48 /javascript/login.js (1082) > 16:20:48 /layout/modern_curve/images/css/bg.png (587) > 16:20:48 /layout/modern_curve/images/css/bg_header.png (485) > 16:20:48 /layout/modern_curve/images/css/menu_bg.png (466) > 16:20:48 /layout/modern_curve/images/css/block_bg.png (577) > 16:20:49 /layout/modern_curve/images/css/search-right.png (6671) > 16:20:49 /images/buttons/feed.png (896) > 16:20:49 /layout/modern_curve/images/button_help.png (532) > 16:20:49 /layout/modern_curve/images/favicon.ico (1429) > > > -- > http://www.themobilepresenter.com/ > > _______________________________________________ > geeklog-devel mailing list > geeklog-devel at lists.geeklog.net > http://eight.pairlist.net/mailman/listinfo/geeklog-devel > -------------- next part -------------- An HTML attachment was scrubbed... URL: From niemans at nlbox.com Sun Oct 13 06:19:39 2013 From: niemans at nlbox.com (Niemans) Date: Sun, 13 Oct 2013 12:19:39 +0200 Subject: [geeklog-devel] is using iframe wise? In-Reply-To: References: <188EB57F-6634-421C-A899-4D2A9D4E050D@nlbox.com> Message-ID: <3963C0F1-3159-4130-8144-157BD02D79A4@nlbox.com> Of course I googled some, but not these specific terms. So I did and there was no news. The results all warn for using iframes when there is no understanding of the drawbacks if iframes I find that the mentioned drawbacks are exactly the reasons I am tending to using iframes: -- bookmarking not possible: perfect! -- navigation issues: okay. -- style sheets not integrated: hurray! So, my quest was also for possible security issues, specific to using iframes in geeklog. It seems that malicious pages will go undetected; but that will not be the case since all external links are under control. Is this all? Wim Op 13 okt. 2013, om 00:18 heeft Dan Stoner het volgende geschreven: > Google for > > iframes are evil > Iframes are bad > ... > > - Dan Stoner > > On Oct 12, 2013 5:57 PM, "Niemans" wrote: > Hello all, > > to embed an application in a site driven by geeklog, I am considering using iframe to replace the center blocks. > Not to embed bocks in there, but an application that takes a large part of the window. Within the iframe ajax will be used. > > Is this a bad idea, are security issues known when iframe is used? > Is information available on do's and don't 's? > > Thought, help? > > Thanks in advance, > wim niemans ri > > _______________________________________________ > geeklog-devel mailing list > geeklog-devel at lists.geeklog.net > http://eight.pairlist.net/mailman/listinfo/geeklog-devel > _______________________________________________ > geeklog-devel mailing list > geeklog-devel at lists.geeklog.net > http://eight.pairlist.net/mailman/listinfo/geeklog-devel -------------- next part -------------- An HTML attachment was scrubbed... URL: From websitemaster at cogeco.net Sun Oct 13 08:07:17 2013 From: websitemaster at cogeco.net (Tom) Date: Sun, 13 Oct 2013 08:07:17 -0400 Subject: [geeklog-devel] Reducing the number of HTTP requests In-Reply-To: <001801cec7a4$6056ac60$21040520$@cogeco.net> References: <58A0B7C9-8DDD-4069-B46E-5A5FEB56FE63@haun-online.de> <001801cec7a4$6056ac60$21040520$@cogeco.net> Message-ID: <003101cec80c$c30b6630$49223290$@cogeco.net> Just to elaborate on this a bit. I did do a test run for combining all css to use the style.css.php (at least in the Modern Curve theme) so css could be cached by using an etag and speed things up a bit. It worked fine except when there are images involved. With the image paths being hardcoded in the css file and having those paths based on the location of the original css file the image would never display since the style.css.php file is located in the themes directory. I never did see a way around this (unless the original css file is written to have the style.css.php in a specific location) Tom -----Original Message----- From: geeklog-devel-bounces at lists.geeklog.net [mailto:geeklog-devel-bounces at lists.geeklog.net] On Behalf Of Tom Sent: October-12-13 7:40 PM To: 'Geeklog Development' Subject: Re: [geeklog-devel] Reducing the number of HTTP requests >> I see a few obvious things (why are we loading the CSS for polls and captcha on the front page?) Basically for the plugins to support Geeklog 1.8.2 and lower. As of Geeklog 2.0.0 since we generate the entire page at the end we can take into account if an autotag gets called and displays something that requires the css file. With Geeklog 1.8.2 and lower we cannot since the header is one of the first things generated. That being said I think the latest version of the polls plugin now requires Geeklog 2.0.0 so that could be switched. Tom -----Original Message----- From: geeklog-devel-bounces at lists.geeklog.net [mailto:geeklog-devel-bounces at lists.geeklog.net] On Behalf Of Dirk Haun Sent: October-12-13 4:47 PM To: geeklog-devel at lists.geeklog.net Subject: [geeklog-devel] Reducing the number of HTTP requests While hunting down some profile spammers, I noticed (not for the first time) that it does take quite a lot of HTTP requests to load the Geeklog homepage. Below is a list of what it takes to load and display our homepage. These are real numbers, grep'ed from the web server log file just now. First column is a timestamp, followed by the URL and the number of bytes sent. That's 34 HTTP requests. Note that it takes a full six seconds to send everything (1 second to render the page, then 5 seconds until the last resource has been requested). That's not exactly a great response time, to put it mildly. This will get better on subsequent pages, when the browser caches things. But 6 seconds is what it takes for a first-time visitor. (The visitor came from a DSL line and the server wasn't busy at the time) I see a few obvious things (why are we loading the CSS for polls and captcha on the front page?) and a few potential fixes (merge JavaScript files; maybe also some of the images). Other ideas? bye, Dirk --- snip --- 16:20:43 / (11012) 16:20:44 /layout/modern_curve/style.css.php?dir=ltr (59466) 16:20:45 /polls/style.css (1538) 16:20:45 /captcha/style.css (684) 16:20:45 /forum/forum/layout/forum.css (3256) 16:20:45 /layout/modern_curve/images/logo.png (16336) 16:20:45 /javascript/common.js (4244) 16:20:45 /forum/smilies.css.php (1828) 16:20:45 /javascript/jquery.min.js (92923) 16:20:45 /layout/modern_curve/javascript/fix_html.js (1435) 16:20:45 /layout/modern_curve/javascript/confirm.js (501) 16:20:46 /layout/modern_curve/javascript/search.js (1076) 16:20:47 /images/facebook-login-icon.png (845) 16:20:47 /images/twitter-login-icon.png (911) 16:20:47 /images/openid_login_icon.png (812) 16:20:47 /layout/modern_curve/images/print.png (756) 16:20:48 /images/topics/announcements.png (3847) 16:20:48 /images/topics/plugins.png (2717) 16:20:48 /images/buttons/download.png (6977) 16:20:48 /docs/images/de.png (694) 16:20:48 /docs/images/pl.png (631) 16:20:48 /docs/images/jp.png (641) 16:20:48 /docs/images/fr.png (675) 16:20:48 /docs/images/es.png (687) 16:20:48 /javascript/fix_tooltips.js (1596) 16:20:48 /javascript/login.js (1082) 16:20:48 /layout/modern_curve/images/css/bg.png (587) 16:20:48 /layout/modern_curve/images/css/bg_header.png (485) 16:20:48 /layout/modern_curve/images/css/menu_bg.png (466) 16:20:48 /layout/modern_curve/images/css/block_bg.png (577) 16:20:49 /layout/modern_curve/images/css/search-right.png (6671) 16:20:49 /images/buttons/feed.png (896) 16:20:49 /layout/modern_curve/images/button_help.png (532) 16:20:49 /layout/modern_curve/images/favicon.ico (1429) -- http://www.themobilepresenter.com/ _______________________________________________ geeklog-devel mailing list geeklog-devel at lists.geeklog.net http://eight.pairlist.net/mailman/listinfo/geeklog-devel _______________________________________________ geeklog-devel mailing list geeklog-devel at lists.geeklog.net http://eight.pairlist.net/mailman/listinfo/geeklog-devel From niemans at nlbox.com Sun Oct 13 09:48:59 2013 From: niemans at nlbox.com (Niemans) Date: Sun, 13 Oct 2013 15:48:59 +0200 Subject: [geeklog-devel] Reducing the number of HTTP requests In-Reply-To: <003101cec80c$c30b6630$49223290$@cogeco.net> References: <58A0B7C9-8DDD-4069-B46E-5A5FEB56FE63@haun-online.de> <001801cec7a4$6056ac60$21040520$@cogeco.net> <003101cec80c$c30b6630$49223290$@cogeco.net> Message-ID: <5E4F956A-718A-418A-9580-29774C3D2D0B@nlbox.com> Some js-files are not exciting and should be discarded: common.js (only for Admin), confirm.js (what?), search.js (can be done in css). Some others are useful and have an odd name. Group them all in one file called glUtilities.js. Some blocks use images and the loading can de delayed. Adding it up: remove polls : save 2 requests remove captcha: save 1 request remove forum: save 2 requests remove common.js: save 1 request colate fix_html.js, confirm.js, search.js into utilities.js: save 2 requests Total 8 requests saved. Than use lazy-loading of images in blocks. Saves you > 10 requests on page load. Well, in the case Dirk showed. Wim Op 13 okt. 2013, om 14:07 heeft Tom het volgende geschreven: > Just to elaborate on this a bit. > > I did do a test run for combining all css to use the style.css.php (at least > in the Modern Curve theme) so css could be cached by using an etag and speed > things up a bit. > > It worked fine except when there are images involved. With the image paths > being hardcoded in the css file and having those paths based on the location > of the original css file the image would never display since the > style.css.php file is located in the themes directory. > > I never did see a way around this (unless the original css file is written > to have the style.css.php in a specific location) > > Tom > > -----Original Message----- > From: geeklog-devel-bounces at lists.geeklog.net > [mailto:geeklog-devel-bounces at lists.geeklog.net] On Behalf Of Tom > Sent: October-12-13 7:40 PM > To: 'Geeklog Development' > Subject: Re: [geeklog-devel] Reducing the number of HTTP requests > >>> I see a few obvious things (why are we loading the CSS for polls > and captcha on the front page?) > > Basically for the plugins to support Geeklog 1.8.2 and lower. As of > Geeklog 2.0.0 since we generate the entire page at the end we can take into > account if an autotag gets called and displays something that requires the > css file. With Geeklog 1.8.2 and lower we cannot since the header is one of > the first things generated. That being said I think the latest version of > the polls plugin now requires Geeklog 2.0.0 so that could be switched. > > > Tom > > > > > > -----Original Message----- > From: geeklog-devel-bounces at lists.geeklog.net > [mailto:geeklog-devel-bounces at lists.geeklog.net] On Behalf Of Dirk Haun > Sent: October-12-13 4:47 PM > To: geeklog-devel at lists.geeklog.net > Subject: [geeklog-devel] Reducing the number of HTTP requests > > While hunting down some profile spammers, I noticed (not for the first time) > that it does take quite a lot of HTTP requests to load the Geeklog homepage. > > Below is a list of what it takes to load and display our homepage. These are > real numbers, grep'ed from the web server log file just now. First column is > a timestamp, followed by the URL and the number of bytes sent. > > That's 34 HTTP requests. Note that it takes a full six seconds to send > everything (1 second to render the page, then 5 seconds until the last > resource has been requested). That's not exactly a great response time, to > put it mildly. This will get better on subsequent pages, when the browser > caches things. But 6 seconds is what it takes for a first-time visitor. > > (The visitor came from a DSL line and the server wasn't busy at the time) > > I see a few obvious things (why are we loading the CSS for polls and captcha > on the front page?) and a few potential fixes (merge JavaScript files; maybe > also some of the images). > > Other ideas? > > bye, Dirk > > > --- snip --- > 16:20:43 / (11012) > 16:20:44 /layout/modern_curve/style.css.php?dir=ltr (59466) > 16:20:45 /polls/style.css (1538) > 16:20:45 /captcha/style.css (684) > 16:20:45 /forum/forum/layout/forum.css (3256) > 16:20:45 /layout/modern_curve/images/logo.png (16336) > 16:20:45 /javascript/common.js (4244) > 16:20:45 /forum/smilies.css.php (1828) > 16:20:45 /javascript/jquery.min.js (92923) > 16:20:45 /layout/modern_curve/javascript/fix_html.js (1435) > 16:20:45 /layout/modern_curve/javascript/confirm.js (501) > 16:20:46 /layout/modern_curve/javascript/search.js (1076) > 16:20:47 /images/facebook-login-icon.png (845) > 16:20:47 /images/twitter-login-icon.png (911) > 16:20:47 /images/openid_login_icon.png (812) > 16:20:47 /layout/modern_curve/images/print.png (756) > 16:20:48 /images/topics/announcements.png (3847) > 16:20:48 /images/topics/plugins.png (2717) > 16:20:48 /images/buttons/download.png (6977) > 16:20:48 /docs/images/de.png (694) > 16:20:48 /docs/images/pl.png (631) > 16:20:48 /docs/images/jp.png (641) > 16:20:48 /docs/images/fr.png (675) > 16:20:48 /docs/images/es.png (687) > 16:20:48 /javascript/fix_tooltips.js (1596) > 16:20:48 /javascript/login.js (1082) > 16:20:48 /layout/modern_curve/images/css/bg.png (587) > 16:20:48 /layout/modern_curve/images/css/bg_header.png (485) > 16:20:48 /layout/modern_curve/images/css/menu_bg.png (466) > 16:20:48 /layout/modern_curve/images/css/block_bg.png (577) > 16:20:49 /layout/modern_curve/images/css/search-right.png (6671) > 16:20:49 /images/buttons/feed.png (896) > 16:20:49 /layout/modern_curve/images/button_help.png (532) > 16:20:49 /layout/modern_curve/images/favicon.ico (1429) > > > -- > http://www.themobilepresenter.com/ > > _______________________________________________ > geeklog-devel mailing list > geeklog-devel at lists.geeklog.net > http://eight.pairlist.net/mailman/listinfo/geeklog-devel > > _______________________________________________ > geeklog-devel mailing list > geeklog-devel at lists.geeklog.net > http://eight.pairlist.net/mailman/listinfo/geeklog-devel > > _______________________________________________ > geeklog-devel mailing list > geeklog-devel at lists.geeklog.net > http://eight.pairlist.net/mailman/listinfo/geeklog-devel > From websitemaster at cogeco.net Sun Oct 13 10:03:21 2013 From: websitemaster at cogeco.net (Tom) Date: Sun, 13 Oct 2013 10:03:21 -0400 Subject: [geeklog-devel] Reducing the number of HTTP requests In-Reply-To: <5E4F956A-718A-418A-9580-29774C3D2D0B@nlbox.com> References: <58A0B7C9-8DDD-4069-B46E-5A5FEB56FE63@haun-online.de> <001801cec7a4$6056ac60$21040520$@cogeco.net> <003101cec80c$c30b6630$49223290$@cogeco.net> <5E4F956A-718A-418A-9580-29774C3D2D0B@nlbox.com> Message-ID: <003b01cec81c$f9c8f7e0$ed5ae7a0$@cogeco.net> >> colate fix_html.js, confirm.js, search.js into utilities.js: save 2 requests Some of these are theme specific so there should be on glutilities.js and one modern_curve.js (or called gltheme or whatever). -----Original Message----- From: geeklog-devel-bounces at lists.geeklog.net [mailto:geeklog-devel-bounces at lists.geeklog.net] On Behalf Of Niemans Sent: October-13-13 9:49 AM To: Geeklog Development Subject: Re: [geeklog-devel] Reducing the number of HTTP requests Some js-files are not exciting and should be discarded: common.js (only for Admin), confirm.js (what?), search.js (can be done in css). Some others are useful and have an odd name. Group them all in one file called glUtilities.js. Some blocks use images and the loading can de delayed. Adding it up: remove polls : save 2 requests remove captcha: save 1 request remove forum: save 2 requests remove common.js: save 1 request colate fix_html.js, confirm.js, search.js into utilities.js: save 2 requests Total 8 requests saved. Than use lazy-loading of images in blocks. Saves you > 10 requests on page load. Well, in the case Dirk showed. Wim Op 13 okt. 2013, om 14:07 heeft Tom het volgende geschreven: > Just to elaborate on this a bit. > > I did do a test run for combining all css to use the style.css.php (at > least in the Modern Curve theme) so css could be cached by using an > etag and speed things up a bit. > > It worked fine except when there are images involved. With the image > paths being hardcoded in the css file and having those paths based on > the location of the original css file the image would never display > since the style.css.php file is located in the themes directory. > > I never did see a way around this (unless the original css file is > written to have the style.css.php in a specific location) > > Tom > > -----Original Message----- > From: geeklog-devel-bounces at lists.geeklog.net > [mailto:geeklog-devel-bounces at lists.geeklog.net] On Behalf Of Tom > Sent: October-12-13 7:40 PM > To: 'Geeklog Development' > Subject: Re: [geeklog-devel] Reducing the number of HTTP requests > >>> I see a few obvious things (why are we loading the CSS for polls > and captcha on the front page?) > > Basically for the plugins to support Geeklog 1.8.2 and lower. > As of Geeklog 2.0.0 since we generate the entire page at the end we > can take into account if an autotag gets called and displays something > that requires the css file. With Geeklog 1.8.2 and lower we cannot > since the header is one of the first things generated. That being said > I think the latest version of the polls plugin now requires Geeklog 2.0.0 so that could be switched. > > > Tom > > > > > > -----Original Message----- > From: geeklog-devel-bounces at lists.geeklog.net > [mailto:geeklog-devel-bounces at lists.geeklog.net] On Behalf Of Dirk > Haun > Sent: October-12-13 4:47 PM > To: geeklog-devel at lists.geeklog.net > Subject: [geeklog-devel] Reducing the number of HTTP requests > > While hunting down some profile spammers, I noticed (not for the first > time) that it does take quite a lot of HTTP requests to load the Geeklog homepage. > > Below is a list of what it takes to load and display our homepage. > These are real numbers, grep'ed from the web server log file just now. > First column is a timestamp, followed by the URL and the number of bytes sent. > > That's 34 HTTP requests. Note that it takes a full six seconds to send > everything (1 second to render the page, then 5 seconds until the last > resource has been requested). That's not exactly a great response > time, to put it mildly. This will get better on subsequent pages, when > the browser caches things. But 6 seconds is what it takes for a first-time visitor. > > (The visitor came from a DSL line and the server wasn't busy at the > time) > > I see a few obvious things (why are we loading the CSS for polls and > captcha on the front page?) and a few potential fixes (merge > JavaScript files; maybe also some of the images). > > Other ideas? > > bye, Dirk > > > --- snip --- > 16:20:43 / (11012) > 16:20:44 /layout/modern_curve/style.css.php?dir=ltr (59466) > 16:20:45 /polls/style.css (1538) > 16:20:45 /captcha/style.css (684) > 16:20:45 /forum/forum/layout/forum.css (3256) > 16:20:45 /layout/modern_curve/images/logo.png (16336) > 16:20:45 /javascript/common.js (4244) > 16:20:45 /forum/smilies.css.php (1828) > 16:20:45 /javascript/jquery.min.js (92923) > 16:20:45 /layout/modern_curve/javascript/fix_html.js (1435) > 16:20:45 /layout/modern_curve/javascript/confirm.js (501) > 16:20:46 /layout/modern_curve/javascript/search.js (1076) > 16:20:47 /images/facebook-login-icon.png (845) > 16:20:47 /images/twitter-login-icon.png (911) > 16:20:47 /images/openid_login_icon.png (812) > 16:20:47 /layout/modern_curve/images/print.png (756) > 16:20:48 /images/topics/announcements.png (3847) > 16:20:48 /images/topics/plugins.png (2717) > 16:20:48 /images/buttons/download.png (6977) > 16:20:48 /docs/images/de.png (694) > 16:20:48 /docs/images/pl.png (631) > 16:20:48 /docs/images/jp.png (641) > 16:20:48 /docs/images/fr.png (675) > 16:20:48 /docs/images/es.png (687) > 16:20:48 /javascript/fix_tooltips.js (1596) > 16:20:48 /javascript/login.js (1082) > 16:20:48 /layout/modern_curve/images/css/bg.png (587) > 16:20:48 /layout/modern_curve/images/css/bg_header.png (485) > 16:20:48 /layout/modern_curve/images/css/menu_bg.png (466) > 16:20:48 /layout/modern_curve/images/css/block_bg.png (577) > 16:20:49 /layout/modern_curve/images/css/search-right.png (6671) > 16:20:49 /images/buttons/feed.png (896) > 16:20:49 /layout/modern_curve/images/button_help.png (532) > 16:20:49 /layout/modern_curve/images/favicon.ico (1429) > > > -- > http://www.themobilepresenter.com/ > > _______________________________________________ > geeklog-devel mailing list > geeklog-devel at lists.geeklog.net > http://eight.pairlist.net/mailman/listinfo/geeklog-devel > > _______________________________________________ > geeklog-devel mailing list > geeklog-devel at lists.geeklog.net > http://eight.pairlist.net/mailman/listinfo/geeklog-devel > > _______________________________________________ > geeklog-devel mailing list > geeklog-devel at lists.geeklog.net > http://eight.pairlist.net/mailman/listinfo/geeklog-devel > _______________________________________________ geeklog-devel mailing list geeklog-devel at lists.geeklog.net http://eight.pairlist.net/mailman/listinfo/geeklog-devel From websitemaster at cogeco.net Mon Oct 14 21:44:05 2013 From: websitemaster at cogeco.net (Tom) Date: Mon, 14 Oct 2013 21:44:05 -0400 Subject: [geeklog-devel] Geeklog Caching Message-ID: <001601cec948$0824c9a0$186e5ce0$@cogeco.net> Okay I have the article caching pretty much done. It works the same way as for staticpage and blocks where you can set an individual story to cache from 0 to X seconds before it is recreated (0 is off which is the default setting). I have 2 questions which applies to all 3 objects being cached (article, staticpages, blocks). 1) Do we want an always on cache option where the cache file is never recreated unless the object is updated by the user. I can see it working where the user enters a -1 (instead of a 0 to X) so the cache file is always used. 2) Right now all cache times default to 0 (off). Do we want 3 config options to allow the user to set some other default? With tests on my windows system I found very little gain in caching articles, staticpages, blocks that have little more than text in them (hundreds of a second difference). Where you really see a savings is when these objects have to do some processing like with embedded autotags, php, etc. At this point how long you want to cache the object for before it is recreated depends on what the data is and if it ever changes and how often. Thoughts? Tom -----Original Message----- From: geeklog-devel-bounces at lists.geeklog.net [mailto:geeklog-devel-bounces at lists.geeklog.net] On Behalf Of Tom Sent: October-13-13 10:03 AM To: 'Geeklog Development' Subject: Re: [geeklog-devel] Reducing the number of HTTP requests >> colate fix_html.js, confirm.js, search.js into utilities.js: save 2 requests Some of these are theme specific so there should be on glutilities.js and one modern_curve.js (or called gltheme or whatever). -----Original Message----- From: geeklog-devel-bounces at lists.geeklog.net [mailto:geeklog-devel-bounces at lists.geeklog.net] On Behalf Of Niemans Sent: October-13-13 9:49 AM To: Geeklog Development Subject: Re: [geeklog-devel] Reducing the number of HTTP requests Some js-files are not exciting and should be discarded: common.js (only for Admin), confirm.js (what?), search.js (can be done in css). Some others are useful and have an odd name. Group them all in one file called glUtilities.js. Some blocks use images and the loading can de delayed. Adding it up: remove polls : save 2 requests remove captcha: save 1 request remove forum: save 2 requests remove common.js: save 1 request colate fix_html.js, confirm.js, search.js into utilities.js: save 2 requests Total 8 requests saved. Than use lazy-loading of images in blocks. Saves you > 10 requests on page load. Well, in the case Dirk showed. Wim Op 13 okt. 2013, om 14:07 heeft Tom het volgende geschreven: > Just to elaborate on this a bit. > > I did do a test run for combining all css to use the style.css.php (at > least in the Modern Curve theme) so css could be cached by using an > etag and speed things up a bit. > > It worked fine except when there are images involved. With the image > paths being hardcoded in the css file and having those paths based on > the location of the original css file the image would never display > since the style.css.php file is located in the themes directory. > > I never did see a way around this (unless the original css file is > written to have the style.css.php in a specific location) > > Tom > > -----Original Message----- > From: geeklog-devel-bounces at lists.geeklog.net > [mailto:geeklog-devel-bounces at lists.geeklog.net] On Behalf Of Tom > Sent: October-12-13 7:40 PM > To: 'Geeklog Development' > Subject: Re: [geeklog-devel] Reducing the number of HTTP requests > >>> I see a few obvious things (why are we loading the CSS for polls > and captcha on the front page?) > > Basically for the plugins to support Geeklog 1.8.2 and lower. > As of Geeklog 2.0.0 since we generate the entire page at the end we > can take into account if an autotag gets called and displays something > that requires the css file. With Geeklog 1.8.2 and lower we cannot > since the header is one of the first things generated. That being said > I think the latest version of the polls plugin now requires Geeklog > 2.0.0 so that could be switched. > > > Tom > > > > > > -----Original Message----- > From: geeklog-devel-bounces at lists.geeklog.net > [mailto:geeklog-devel-bounces at lists.geeklog.net] On Behalf Of Dirk > Haun > Sent: October-12-13 4:47 PM > To: geeklog-devel at lists.geeklog.net > Subject: [geeklog-devel] Reducing the number of HTTP requests > > While hunting down some profile spammers, I noticed (not for the first > time) that it does take quite a lot of HTTP requests to load the > Geeklog homepage. > > Below is a list of what it takes to load and display our homepage. > These are real numbers, grep'ed from the web server log file just now. > First column is a timestamp, followed by the URL and the number of > bytes sent. > > That's 34 HTTP requests. Note that it takes a full six seconds to send > everything (1 second to render the page, then 5 seconds until the last > resource has been requested). That's not exactly a great response > time, to put it mildly. This will get better on subsequent pages, when > the browser caches things. But 6 seconds is what it takes for a > first-time visitor. > > (The visitor came from a DSL line and the server wasn't busy at the > time) > > I see a few obvious things (why are we loading the CSS for polls and > captcha on the front page?) and a few potential fixes (merge > JavaScript files; maybe also some of the images). > > Other ideas? > > bye, Dirk > > > --- snip --- > 16:20:43 / (11012) > 16:20:44 /layout/modern_curve/style.css.php?dir=ltr (59466) > 16:20:45 /polls/style.css (1538) > 16:20:45 /captcha/style.css (684) > 16:20:45 /forum/forum/layout/forum.css (3256) > 16:20:45 /layout/modern_curve/images/logo.png (16336) > 16:20:45 /javascript/common.js (4244) > 16:20:45 /forum/smilies.css.php (1828) > 16:20:45 /javascript/jquery.min.js (92923) > 16:20:45 /layout/modern_curve/javascript/fix_html.js (1435) > 16:20:45 /layout/modern_curve/javascript/confirm.js (501) > 16:20:46 /layout/modern_curve/javascript/search.js (1076) > 16:20:47 /images/facebook-login-icon.png (845) > 16:20:47 /images/twitter-login-icon.png (911) > 16:20:47 /images/openid_login_icon.png (812) > 16:20:47 /layout/modern_curve/images/print.png (756) > 16:20:48 /images/topics/announcements.png (3847) > 16:20:48 /images/topics/plugins.png (2717) > 16:20:48 /images/buttons/download.png (6977) > 16:20:48 /docs/images/de.png (694) > 16:20:48 /docs/images/pl.png (631) > 16:20:48 /docs/images/jp.png (641) > 16:20:48 /docs/images/fr.png (675) > 16:20:48 /docs/images/es.png (687) > 16:20:48 /javascript/fix_tooltips.js (1596) > 16:20:48 /javascript/login.js (1082) > 16:20:48 /layout/modern_curve/images/css/bg.png (587) > 16:20:48 /layout/modern_curve/images/css/bg_header.png (485) > 16:20:48 /layout/modern_curve/images/css/menu_bg.png (466) > 16:20:48 /layout/modern_curve/images/css/block_bg.png (577) > 16:20:49 /layout/modern_curve/images/css/search-right.png (6671) > 16:20:49 /images/buttons/feed.png (896) > 16:20:49 /layout/modern_curve/images/button_help.png (532) > 16:20:49 /layout/modern_curve/images/favicon.ico (1429) > > > -- > http://www.themobilepresenter.com/ > > _______________________________________________ > geeklog-devel mailing list > geeklog-devel at lists.geeklog.net > http://eight.pairlist.net/mailman/listinfo/geeklog-devel > > _______________________________________________ > geeklog-devel mailing list > geeklog-devel at lists.geeklog.net > http://eight.pairlist.net/mailman/listinfo/geeklog-devel > > _______________________________________________ > geeklog-devel mailing list > geeklog-devel at lists.geeklog.net > http://eight.pairlist.net/mailman/listinfo/geeklog-devel > _______________________________________________ geeklog-devel mailing list geeklog-devel at lists.geeklog.net http://eight.pairlist.net/mailman/listinfo/geeklog-devel _______________________________________________ geeklog-devel mailing list geeklog-devel at lists.geeklog.net http://eight.pairlist.net/mailman/listinfo/geeklog-devel From ironmax at spacequad.com Tue Oct 15 17:52:27 2013 From: ironmax at spacequad.com (Michael Brusletten) Date: Tue, 15 Oct 2013 17:52:27 -0400 Subject: [geeklog-devel] geeklog-devel Digest, Vol 85, Issue 9 In-Reply-To: References: Message-ID: <8116F86B37544ABD9C219DCCC3A5D1A1@Node5> I wonder if making the cache options available per article, staticpage, and block with a default configured in the main configuration. This way the admin can decide on whats constantly changing or not. I would suspect that the stories would not change much, but then again, there could be items in the stories that might change from outside sources, like maybe images or banners. Michael ---------------------------------------------------------------------- Message: 1 Date: Mon, 14 Oct 2013 21:44:05 -0400 From: "Tom" Subject: [geeklog-devel] Geeklog Caching To: "'Geeklog Development'" Message-ID: <001601cec948$0824c9a0$186e5ce0$@cogeco.net> Content-Type: text/plain; charset="us-ascii" Okay I have the article caching pretty much done. It works the same way as for staticpage and blocks where you can set an individual story to cache from 0 to X seconds before it is recreated (0 is off which is the default setting). I have 2 questions which applies to all 3 objects being cached (article, staticpages, blocks). 1) Do we want an always on cache option where the cache file is never recreated unless the object is updated by the user. I can see it working where the user enters a -1 (instead of a 0 to X) so the cache file is always used. 2) Right now all cache times default to 0 (off). Do we want 3 config options to allow the user to set some other default? With tests on my windows system I found very little gain in caching articles, staticpages, blocks that have little more than text in them (hundreds of a second difference). Where you really see a savings is when these objects have to do some processing like with embedded autotags, php, etc. At this point how long you want to cache the object for before it is recreated depends on what the data is and if it ever changes and how often. Thoughts? Tom From websitemaster at cogeco.net Tue Oct 15 19:23:16 2013 From: websitemaster at cogeco.net (Tom) Date: Tue, 15 Oct 2013 19:23:16 -0400 Subject: [geeklog-devel] geeklog-devel Digest, Vol 85, Issue 9 In-Reply-To: <8116F86B37544ABD9C219DCCC3A5D1A1@Node5> References: <8116F86B37544ABD9C219DCCC3A5D1A1@Node5> Message-ID: <004601cec9fd$86f4c4a0$94de4de0$@cogeco.net> All object cache values can be set individually. I was just wondering if we wanted customizable default value for any new objects. We current plan is to add it in. Tom -----Original Message----- From: geeklog-devel-bounces at lists.geeklog.net [mailto:geeklog-devel-bounces at lists.geeklog.net] On Behalf Of Michael Brusletten Sent: October-15-13 5:52 PM To: geeklog-devel at lists.geeklog.net Subject: Re: [geeklog-devel] geeklog-devel Digest, Vol 85, Issue 9 I wonder if making the cache options available per article, staticpage, and block with a default configured in the main configuration. This way the admin can decide on whats constantly changing or not. I would suspect that the stories would not change much, but then again, there could be items in the stories that might change from outside sources, like maybe images or banners. Michael ---------------------------------------------------------------------- Message: 1 Date: Mon, 14 Oct 2013 21:44:05 -0400 From: "Tom" Subject: [geeklog-devel] Geeklog Caching To: "'Geeklog Development'" Message-ID: <001601cec948$0824c9a0$186e5ce0$@cogeco.net> Content-Type: text/plain; charset="us-ascii" Okay I have the article caching pretty much done. It works the same way as for staticpage and blocks where you can set an individual story to cache from 0 to X seconds before it is recreated (0 is off which is the default setting). I have 2 questions which applies to all 3 objects being cached (article, staticpages, blocks). 1) Do we want an always on cache option where the cache file is never recreated unless the object is updated by the user. I can see it working where the user enters a -1 (instead of a 0 to X) so the cache file is always used. 2) Right now all cache times default to 0 (off). Do we want 3 config options to allow the user to set some other default? With tests on my windows system I found very little gain in caching articles, staticpages, blocks that have little more than text in them (hundreds of a second difference). Where you really see a savings is when these objects have to do some processing like with embedded autotags, php, etc. At this point how long you want to cache the object for before it is recreated depends on what the data is and if it ever changes and how often. Thoughts? Tom _______________________________________________ geeklog-devel mailing list geeklog-devel at lists.geeklog.net http://eight.pairlist.net/mailman/listinfo/geeklog-devel From ironmax at spacequad.com Wed Oct 16 17:56:33 2013 From: ironmax at spacequad.com (Michael Brusletten) Date: Wed, 16 Oct 2013 17:56:33 -0400 Subject: [geeklog-devel] geeklog-devel Digest, Vol 85, Issue 10 In-Reply-To: References: Message-ID: Tom, That sounds good to me. Everything should be covered under this plan. Any new plugins (or legacy plugins slated for upgrades) can take advantage of this new feature by having individual plugin config options. The older plugins that have not been upgraded, should be able to work fine as your working with them now, because they would fall under one of the three areas, articles, staticpages, and blocks. Are there variable hooks that allow for this, where the plugin can use when the author of the plugin decides to upgrade? Michael -----Original Message----- Message: 2 Date: Tue, 15 Oct 2013 19:23:16 -0400 From: "Tom" Subject: Re: [geeklog-devel] geeklog-devel Digest, Vol 85, Issue 9 To: "'Geeklog Development'" Message-ID: <004601cec9fd$86f4c4a0$94de4de0$@cogeco.net> Content-Type: text/plain; charset="us-ascii" All object cache values can be set individually. I was just wondering if we wanted customizable default value for any new objects. We current plan is to add it in. Tom -----Original Message----- From: geeklog-devel-bounces at lists.geeklog.net [mailto:geeklog-devel-bounces at lists.geeklog.net] On Behalf Of Michael Brusletten Sent: October-15-13 5:52 PM To: geeklog-devel at lists.geeklog.net Subject: Re: [geeklog-devel] geeklog-devel Digest, Vol 85, Issue 9 I wonder if making the cache options available per article, staticpage, and block with a default configured in the main configuration. This way the admin can decide on whats constantly changing or not. I would suspect that the stories would not change much, but then again, there could be items in the stories that might change from outside sources, like maybe images or banners. Michael ---------------------------------------------------------------------- Message: 1 Date: Mon, 14 Oct 2013 21:44:05 -0400 From: "Tom" Subject: [geeklog-devel] Geeklog Caching To: "'Geeklog Development'" Message-ID: <001601cec948$0824c9a0$186e5ce0$@cogeco.net> Content-Type: text/plain; charset="us-ascii" Okay I have the article caching pretty much done. It works the same way as for staticpage and blocks where you can set an individual story to cache from 0 to X seconds before it is recreated (0 is off which is the default setting). I have 2 questions which applies to all 3 objects being cached (article, staticpages, blocks). 1) Do we want an always on cache option where the cache file is never recreated unless the object is updated by the user. I can see it working where the user enters a -1 (instead of a 0 to X) so the cache file is always used. 2) Right now all cache times default to 0 (off). Do we want 3 config options to allow the user to set some other default? With tests on my windows system I found very little gain in caching articles, staticpages, blocks that have little more than text in them (hundreds of a second difference). Where you really see a savings is when these objects have to do some processing like with embedded autotags, php, etc. At this point how long you want to cache the object for before it is recreated depends on what the data is and if it ever changes and how often. Thoughts? Tom _______________________________________________ From websitemaster at cogeco.net Wed Oct 16 21:59:12 2013 From: websitemaster at cogeco.net (Tom) Date: Wed, 16 Oct 2013 21:59:12 -0400 Subject: [geeklog-devel] geeklog-devel Digest, Vol 85, Issue 10 In-Reply-To: References: Message-ID: <00cf01cecadc$7a088e40$6e19aac0$@cogeco.net> The older plugins will work with the template caching automatically. There items text, etc.. would not be directly cached though. The plugin would have to be updated to support that which is fairly easy to do with the built in api (which the staticpage plugin, blocks, etc.. can be used as examples). BTW I have had a few hiccups with the Article Caching. At one point I had the entire story being cached (Everything from the Title, date, etc.., down to the number of comments). I have pulled back from this since there are too many config values that can change things along with an article can belong to more than one topic (so a version of the article would have to be saved for each topic it belongs too). I think I may just end up caching just the intro text and the body text (which is something you would only do if it had autotags in it). I will have to do a bit more testing to see what I decide to do. I also have to make sure page breaks etc.. work with all this. Tom -----Original Message----- From: geeklog-devel-bounces at lists.geeklog.net [mailto:geeklog-devel-bounces at lists.geeklog.net] On Behalf Of Michael Brusletten Sent: October-16-13 5:57 PM To: geeklog-devel at lists.geeklog.net Subject: Re: [geeklog-devel] geeklog-devel Digest, Vol 85, Issue 10 Tom, That sounds good to me. Everything should be covered under this plan. Any new plugins (or legacy plugins slated for upgrades) can take advantage of this new feature by having individual plugin config options. The older plugins that have not been upgraded, should be able to work fine as your working with them now, because they would fall under one of the three areas, articles, staticpages, and blocks. Are there variable hooks that allow for this, where the plugin can use when the author of the plugin decides to upgrade? Michael -----Original Message----- Message: 2 Date: Tue, 15 Oct 2013 19:23:16 -0400 From: "Tom" Subject: Re: [geeklog-devel] geeklog-devel Digest, Vol 85, Issue 9 To: "'Geeklog Development'" Message-ID: <004601cec9fd$86f4c4a0$94de4de0$@cogeco.net> Content-Type: text/plain; charset="us-ascii" All object cache values can be set individually. I was just wondering if we wanted customizable default value for any new objects. We current plan is to add it in. Tom -----Original Message----- From: geeklog-devel-bounces at lists.geeklog.net [mailto:geeklog-devel-bounces at lists.geeklog.net] On Behalf Of Michael Brusletten Sent: October-15-13 5:52 PM To: geeklog-devel at lists.geeklog.net Subject: Re: [geeklog-devel] geeklog-devel Digest, Vol 85, Issue 9 I wonder if making the cache options available per article, staticpage, and block with a default configured in the main configuration. This way the admin can decide on whats constantly changing or not. I would suspect that the stories would not change much, but then again, there could be items in the stories that might change from outside sources, like maybe images or banners. Michael ---------------------------------------------------------------------- Message: 1 Date: Mon, 14 Oct 2013 21:44:05 -0400 From: "Tom" Subject: [geeklog-devel] Geeklog Caching To: "'Geeklog Development'" Message-ID: <001601cec948$0824c9a0$186e5ce0$@cogeco.net> Content-Type: text/plain; charset="us-ascii" Okay I have the article caching pretty much done. It works the same way as for staticpage and blocks where you can set an individual story to cache from 0 to X seconds before it is recreated (0 is off which is the default setting). I have 2 questions which applies to all 3 objects being cached (article, staticpages, blocks). 1) Do we want an always on cache option where the cache file is never recreated unless the object is updated by the user. I can see it working where the user enters a -1 (instead of a 0 to X) so the cache file is always used. 2) Right now all cache times default to 0 (off). Do we want 3 config options to allow the user to set some other default? With tests on my windows system I found very little gain in caching articles, staticpages, blocks that have little more than text in them (hundreds of a second difference). Where you really see a savings is when these objects have to do some processing like with embedded autotags, php, etc. At this point how long you want to cache the object for before it is recreated depends on what the data is and if it ever changes and how often. Thoughts? Tom _______________________________________________ _______________________________________________ geeklog-devel mailing list geeklog-devel at lists.geeklog.net http://eight.pairlist.net/mailman/listinfo/geeklog-devel From joe at throwingdice.com Thu Oct 17 01:07:20 2013 From: joe at throwingdice.com (Joe Mucchiello) Date: Thu, 17 Oct 2013 00:07:20 -0500 Subject: [geeklog-devel] geeklog-devel Digest, Vol 85, Issue 10 In-Reply-To: <00cf01cecadc$7a088e40$6e19aac0$@cogeco.net> References: <00cf01cecadc$7a088e40$6e19aac0$@cogeco.net> Message-ID: <446453579e8f3c984c96605fe9131718.squirrel@mustang.hawkhost.com> > BTW I have had a few hiccups with the Article Caching. At one point I had > the entire story being cached (Everything from the Title, date, etc.., > down to the number of comments). Are you using the $nocache field on the set_var function? One of the fields that should not be cached is date since the date format is user configurable. So you call set_var() with $nocache = true so that the cached file still pulls the variable from the template. function set_var($varname, $value = "", $append = false, $nocache = false) From websitemaster at cogeco.net Thu Oct 17 06:59:10 2013 From: websitemaster at cogeco.net (Tom) Date: Thu, 17 Oct 2013 06:59:10 -0400 Subject: [geeklog-devel] geeklog-devel Digest, Vol 85, Issue 10 In-Reply-To: <446453579e8f3c984c96605fe9131718.squirrel@mustang.hawkhost.com> References: <00cf01cecadc$7a088e40$6e19aac0$@cogeco.net> <446453579e8f3c984c96605fe9131718.squirrel@mustang.hawkhost.com> Message-ID: <00fd01cecb27$e85f0ef0$b91d2cd0$@cogeco.net> No I had forgotten about the date thanks Joe. There are also a number of $_CONF values that I have to trap for and delete the article cache files if they change like allow_page_breaks, article_image_align, allow_user_photo, etc.. I also need to delete cache files if a user changes his user information. With Geeklog allowing stories to belong to more than one topics I also have to make sure the topic icon and bread crumb stuff is ether not cached (like the story date) or I create a separate article cache file for each topic. The last thing I notice (and this is kind of what made me rethink things) was that caching through the template like so $article->check_instance($instance_id, $article_filevar) Means that template caching must be enabled and there is no built in way to reset these files after a certain time period (I am thinking about autotags in articles here that need to be refreshed every so often). That is why I am thinking of using the other functions instead ie CACHE_check_instance($cacheInstance) Tom -----Original Message----- From: geeklog-devel-bounces at lists.geeklog.net [mailto:geeklog-devel-bounces at lists.geeklog.net] On Behalf Of Joe Mucchiello Sent: October-17-13 1:07 AM To: Geeklog Development Subject: Re: [geeklog-devel] geeklog-devel Digest, Vol 85, Issue 10 > BTW I have had a few hiccups with the Article Caching. At one point I > had the entire story being cached (Everything from the Title, date, > etc.., down to the number of comments). Are you using the $nocache field on the set_var function? One of the fields that should not be cached is date since the date format is user configurable. So you call set_var() with $nocache = true so that the cached file still pulls the variable from the template. function set_var($varname, $value = "", $append = false, $nocache = false) _______________________________________________ geeklog-devel mailing list geeklog-devel at lists.geeklog.net http://eight.pairlist.net/mailman/listinfo/geeklog-devel From joe at throwingdice.com Thu Oct 17 23:00:03 2013 From: joe at throwingdice.com (Joe Mucchiello) Date: Thu, 17 Oct 2013 22:00:03 -0500 Subject: [geeklog-devel] geeklog-devel Digest, Vol 85, Issue 10 In-Reply-To: <00fd01cecb27$e85f0ef0$b91d2cd0$@cogeco.net> References: <00cf01cecadc$7a088e40$6e19aac0$@cogeco.net> <446453579e8f3c984c96605fe9131718.squirrel@mustang.hawkhost.com> <00fd01cecb27$e85f0ef0$b91d2cd0$@cogeco.net> Message-ID: <23e7e475a8242d813fe2117a89829ac3.squirrel@mustang.hawkhost.com> > CACHE_check_instance($cacheInstance) Unfortunately I have completely forgotten the specifics behind how to do the cache stuff so if you need an example, look at the glFusion code. Caching of articles was the first use of the instance cache stuff. IIRC there's an if and if the cache is "fresh" you set the 4-6 variables that can't be cached and it pulls the article from cache. If the else path is taken, you build the whole article, setting those 4-6 variables as $nocache and add the instance to the cache. I think the devil in the details was naming the instance. You might name it uniquely per topic or have anonymous versions separate from non-anon versions. Generating the instance name correctly took Mark a few tries. From websitemaster at cogeco.net Fri Oct 18 07:15:06 2013 From: websitemaster at cogeco.net (Tom) Date: Fri, 18 Oct 2013 07:15:06 -0400 Subject: [geeklog-devel] geeklog-devel Digest, Vol 85, Issue 10 In-Reply-To: <23e7e475a8242d813fe2117a89829ac3.squirrel@mustang.hawkhost.com> References: <00cf01cecadc$7a088e40$6e19aac0$@cogeco.net> <446453579e8f3c984c96605fe9131718.squirrel@mustang.hawkhost.com> <00fd01cecb27$e85f0ef0$b91d2cd0$@cogeco.net> <23e7e475a8242d813fe2117a89829ac3.squirrel@mustang.hawkhost.com> Message-ID: <017301cecbf3$4ccd2f90$e6678eb0$@cogeco.net> Hi Joe, Yup I have used Marks work as an example and I have seen how instances are created based on the user, language, theme , etc... I plan to add the topic ids in this way as well The difference with the way the story caching is done (when compared to the other way of using the functions directly ie CACHE_check_instance($cacheInstance) as with the What's New Block) is that it caches it directly into the template cache file. This means if template caching is turned off in the Configuration then the story caching is turned off as well. I am currently trying to find a way around this which probably means a few updates to the template class or by using the functions directly. I have a few ideas yet which I will try out this weekend. Tom -----Original Message----- From: geeklog-devel-bounces at lists.geeklog.net [mailto:geeklog-devel-bounces at lists.geeklog.net] On Behalf Of Joe Mucchiello Sent: October-17-13 11:00 PM To: Geeklog Development Subject: Re: [geeklog-devel] geeklog-devel Digest, Vol 85, Issue 10 > CACHE_check_instance($cacheInstance) Unfortunately I have completely forgotten the specifics behind how to do the cache stuff so if you need an example, look at the glFusion code. Caching of articles was the first use of the instance cache stuff. IIRC there's an if and if the cache is "fresh" you set the 4-6 variables that can't be cached and it pulls the article from cache. If the else path is taken, you build the whole article, setting those 4-6 variables as $nocache and add the instance to the cache. I think the devil in the details was naming the instance. You might name it uniquely per topic or have anonymous versions separate from non-anon versions. Generating the instance name correctly took Mark a few tries. _______________________________________________ geeklog-devel mailing list geeklog-devel at lists.geeklog.net http://eight.pairlist.net/mailman/listinfo/geeklog-devel From hamon.erwan at free.fr Mon Oct 21 16:13:23 2013 From: hamon.erwan at free.fr (Erwan HAMON) Date: Mon, 21 Oct 2013 22:13:23 +0200 Subject: [geeklog-devel] Doing a Geeklog upgrade In-Reply-To: <201310072149.51912.hamon.erwan@free.fr> References: <201310072149.51912.hamon.erwan@free.fr> Message-ID: <201310212213.24630.hamon.erwan@free.fr> Le lundi 7 octobre 2013 21:49, Erwan HAMON a ?crit : >After making good progress on hacking a CLI upgrade process to get it >up to Geeklog 2.0.0, Would you be interested in this CLI upgrade script ? It could be useful for automatic regression testing in Jenkins. I am using it over and over to test my migration with commands like : cd ~/geektest/testgl2/html/admin/install/ ; \ mysql -u root -pXXXX testgl2 < ~/geektest/dropTables.sql ; \ mysql -u root -pXXXX testgl2 < ~/geektest/dumpGeeklog1_4Data.sql ; \ php cli_db_upgrade.php | tee update00.log Regards, -- Erwan HAMON - http://hamon.erwan.free.fr/ From hamon.erwan at free.fr Mon Oct 21 16:13:57 2013 From: hamon.erwan at free.fr (Erwan HAMON) Date: Mon, 21 Oct 2013 22:13:57 +0200 Subject: [geeklog-devel] DB upgrade to default DB schema. Message-ID: <201310212213.58421.hamon.erwan@free.fr> Hi, If you install a really old version of Geeklog (eg: 1.4) then upgrade it to 2.0, the resulting database schema is not exactly the same as if you install a fresh 2.0. This does not help when looking for database customizations. It could also potentially be a source for weird bugs. The attached script will bring an upgraded Geeklog DB schema to exactly the same as a fresh 2.0 install. Regards, -- Erwan HAMON - http://hamon.erwan.free.fr/ -------------- next part -------------- A non-text attachment was scrubbed... Name: mysql_fix_2.0.0.php Type: application/x-php Size: 4971 bytes Desc: not available URL: From hamon.erwan at free.fr Mon Oct 21 16:16:37 2013 From: hamon.erwan at free.fr (Erwan HAMON) Date: Mon, 21 Oct 2013 22:16:37 +0200 Subject: [geeklog-devel] Vanishing backslashes in static pages. Message-ID: <201310212216.38610.hamon.erwan@free.fr> Hi, When saving then displaying a static page, backslashes '\' are removed. There are already Mantises related to add/stripslashes so I did not create one. I am surprised there are still many stripslashes() calls in Geeklog's code base. My understanding is that $POST, $_GET and $_COOKIE should go once thru COM_stripslashes. Any SQL query should be built using DB_escapeString(). That should be it. Shouldn't it ? However, there are double addslashed old records in the database. These should be corrected using an utility to be written. Fixing the slashes problem should not be a huge undertaking code-wise. Given the testing requirements it's probably not wise to do it just before 2.1.0's freeze. What are your thoughts ? Regards, -- Erwan HAMON - http://hamon.erwan.free.fr/ From hamon.erwan at free.fr Mon Oct 21 16:23:17 2013 From: hamon.erwan at free.fr (Erwan HAMON) Date: Mon, 21 Oct 2013 22:23:17 +0200 Subject: [geeklog-devel] Theme menu_in_footer and new template engine. Message-ID: <201310212223.17653.hamon.erwan@free.fr> Hi I need to upgrade a couple of themes where {plg_menu_elements} is located in the left column. If I want to use responsive design elements with $_CONF['left_blocks_in_footer'] then I need a corresponding $_CONF['menu_in_footer']. I wrote such a feature in Geeklog 1.7 and ended up putting it in my theme's functions.php [theme]_siteHeader and [theme]_siteFooter. It's still working in Geeklog 2.0. But I'd like to port the theme to the new template engine. I'm not too sure if I need to write a custom [theme]_createHTMLDocument. Or will the new engine simply fill {plg_menu_elements} when it finds it in footer.thtml ? Regards, -- Erwan HAMON - http://hamon.erwan.free.fr/ From websitemaster at cogeco.net Mon Oct 21 20:09:04 2013 From: websitemaster at cogeco.net (Tom) Date: Mon, 21 Oct 2013 20:09:04 -0400 Subject: [geeklog-devel] Theme menu_in_footer and new template engine. In-Reply-To: <201310212223.17653.hamon.erwan@free.fr> References: <201310212223.17653.hamon.erwan@free.fr> Message-ID: <009501ceceba$eb7b2c40$c27184c0$@cogeco.net> This should get you started updating a theme: http://wiki.geeklog.net/index.php/Theme_Developers_Guide http://www.geeklog.net/docs/english/theme.html Do you need {plg_menu_elements} in a block or is it located in an actual template file? If it is in a block you could create an autotag that could retrieve the same information If it is in a template take a look at the CUSTOM_templateSetVars function in lib-custom.php. You could modify that function to retrieve the information as well. Tom -----Original Message----- From: geeklog-devel-bounces at lists.geeklog.net [mailto:geeklog-devel-bounces at lists.geeklog.net] On Behalf Of Erwan HAMON Sent: October-21-13 4:23 PM To: geeklog-devel at lists.geeklog.net Subject: [geeklog-devel] Theme menu_in_footer and new template engine. Hi I need to upgrade a couple of themes where {plg_menu_elements} is located in the left column. If I want to use responsive design elements with $_CONF['left_blocks_in_footer'] then I need a corresponding $_CONF['menu_in_footer']. I wrote such a feature in Geeklog 1.7 and ended up putting it in my theme's functions.php [theme]_siteHeader and [theme]_siteFooter. It's still working in Geeklog 2.0. But I'd like to port the theme to the new template engine. I'm not too sure if I need to write a custom [theme]_createHTMLDocument. Or will the new engine simply fill {plg_menu_elements} when it finds it in footer.thtml ? Regards, -- Erwan HAMON - http://hamon.erwan.free.fr/ _______________________________________________ geeklog-devel mailing list geeklog-devel at lists.geeklog.net http://eight.pairlist.net/mailman/listinfo/geeklog-devel From websitemaster at cogeco.net Mon Oct 21 20:17:42 2013 From: websitemaster at cogeco.net (Tom) Date: Mon, 21 Oct 2013 20:17:42 -0400 Subject: [geeklog-devel] DB upgrade to default DB schema. In-Reply-To: <201310212213.58421.hamon.erwan@free.fr> References: <201310212213.58421.hamon.erwan@free.fr> Message-ID: <009901cecebc$20326470$60972d50$@cogeco.net> What version did you install from? I know we did a pretty in-depth test a couple of years ago on the install process (on a pre 1.5 database) and things seemed to be working fine at that point (once a bug was fixed). Could you create a bug report in our tracker on this along with your sql script of fixes? Thanks Tom -----Original Message----- From: geeklog-devel-bounces at lists.geeklog.net [mailto:geeklog-devel-bounces at lists.geeklog.net] On Behalf Of Erwan HAMON Sent: October-21-13 4:14 PM To: geeklog-devel at lists.geeklog.net Subject: [geeklog-devel] DB upgrade to default DB schema. Hi, If you install a really old version of Geeklog (eg: 1.4) then upgrade it to 2.0, the resulting database schema is not exactly the same as if you install a fresh 2.0. This does not help when looking for database customizations. It could also potentially be a source for weird bugs. The attached script will bring an upgraded Geeklog DB schema to exactly the same as a fresh 2.0 install. Regards, -- Erwan HAMON - http://hamon.erwan.free.fr/ From dirk at haun-online.de Tue Oct 22 01:59:16 2013 From: dirk at haun-online.de (Dirk Haun) Date: Tue, 22 Oct 2013 07:59:16 +0200 Subject: [geeklog-devel] DB upgrade to default DB schema. In-Reply-To: <009901cecebc$20326470$60972d50$@cogeco.net> References: <201310212213.58421.hamon.erwan@free.fr> <009901cecebc$20326470$60972d50$@cogeco.net> Message-ID: <1F36641B-0E36-49D2-A815-CC4B25EEAEC6@haun-online.de> Tom wrote: > What version did you install from? I know we did a pretty in-depth test a couple of years ago on the install process (on a pre 1.5 database) and things seemed to be working fine at that point (once a bug was fixed). I think there were a few cases over the years where we decided that, say, a field didn't have to be an int but that a tinyint would also do - and then we didn't bother to update old databases accordingly. From a quick look at the script, I think most of what Erwan found falls into that category; so they're not strictly bugs, more like inconsistencies. bye, Dirk -- http://www.themobilepresenter.com/ From hamon.erwan at free.fr Tue Oct 22 16:01:33 2013 From: hamon.erwan at free.fr (Erwan HAMON) Date: Tue, 22 Oct 2013 22:01:33 +0200 Subject: [geeklog-devel] DB upgrade to default DB schema. In-Reply-To: <1F36641B-0E36-49D2-A815-CC4B25EEAEC6@haun-online.de> References: <201310212213.58421.hamon.erwan@free.fr> <009901cecebc$20326470$60972d50$@cogeco.net> <1F36641B-0E36-49D2-A815-CC4B25EEAEC6@haun-online.de> Message-ID: <201310222201.35497.hamon.erwan@free.fr> Le mardi 22 octobre 2013 07:59, Dirk Haun a ?crit : >Tom wrote: >> What version did you install from? geeklog-1.3.8-1sr4 I'll fill the bug repport anyway. >> I know we did a pretty in-depth >> test a couple of years ago on the install process (on a pre 1.5 >> database) and things seemed to be working fine at that point (once >> a bug was fixed). > >I think there were a few cases over the years where we decided that, >say, a field didn't have to be an int but that a tinyint would also >do - and then we didn't bother to update old databases accordingly. >From a quick look at the script, I think most of what Erwan found >falls into that category; so they're not strictly bugs, more like >inconsistencies. I agree. Some fixes are down right cosmetic. Like getting indexes in the exact same order. But my point was to have an upgrade script that got exactly to Geeklog 2.0 so that I could apply it to my database and easily track database customisations. I did not want any distraction while parsing diffs. Regards, -- Erwan HAMON - http://hamon.erwan.free.fr/ From websitemaster at cogeco.net Mon Oct 28 17:29:09 2013 From: websitemaster at cogeco.net (Tom) Date: Mon, 28 Oct 2013 17:29:09 -0400 Subject: [geeklog-devel] Geeklog File license and copyright message Message-ID: <021f01ced424$bd4eeae0$37ecc0a0$@cogeco.net> The copyright and Geeklog version message at the top of each Geeklog file get rarely updated. Is there a script or something that can be run to update these automatically (at least with the Geeklog version and updated copyright date? http://www.geeklog.net/forum/viewtopic.php?msg=1&showtopic=95297&lastpost=tr ue#95312 Tom