[geeklog-devel] Geeklog 1.9.0 update

[cordiste]

I added a feature request and a patch in attachment
http://project.geeklog.net/tracking/view.php?id=1434

Ben

2012/3/5 Tom <websitemaster at cogeco.net>:
> Yeah I had thought of that (but no time). Add in a feature request for it
> (and a patch if you are able :-)
>
> Tom
>
> -----Original Message-----
> From: geeklog-devel-bounces at lists.geeklog.net
> [mailto:geeklog-devel-bounces at lists.geeklog.net] On Behalf Of cordiste
> Sent: March-05-12 12:04 PM
> To: Geeklog Development
> Subject: Re: [geeklog-devel] Geeklog 1.9.0 update
>
> Thanks for the exemple.
>
> Maybe we can add a list of the dynamic blocks on the admin block page :
>
> Near line 427 of the admin/block.php file add to listblocks function
> something like:
>
>        $leftblocks = PLG_getBlocks('left');
>        foreach($leftblocks as $block){
>                        $retval .= ADMIN_simpleList('', $header_arr, '',
>                           $leftblocks, $options = '', $form_arr='');
>    }
>
> And something similar for right dynamic blocks. Also, maybe a word or two
> can explain or remind to admins to look at the config for those blocks
> settings.
>
> Ben
>
>
> 2012/3/5 Tom <websitemaster at cogeco.net>:
>> Take a look at the polls plugin in Geeklog 1.9.0 as an example. In the
>> configuration it offers those options.
>>
>>
>>
>> -----Original Message-----
>> From: geeklog-devel-bounces at lists.geeklog.net
>> [mailto:geeklog-devel-bounces at lists.geeklog.net] On Behalf Of cordiste
>> Sent: March-04-12 6:16 PM
>> To: Geeklog Development
>> Subject: Re: [geeklog-devel] Geeklog 1.9.0 update
>>
>> Tom,
>>
>> I tried to install paypal plugin and got the unknown column 'tid' error.
>>
>> The suggested solution is to create a dynamic block, but I also need a
>> config setting to allow admin to choose to display or not this block,
>> plus 2 more settings to choose side and block order.
>>
>> Would there be a preferred solution for centralized management of blocks?
>>
>> Ben
>>
>>
>>
>> 2012/3/4 Tom <websitemaster at cogeco.net>:
>>> Maybe the best spot for the Emergency Rescue Tool would be the
>>> install directory (with a link to it on the main install page). The
>>> install script doesn't break when the site goes down so it should
>>> still be accessible and it will get deleted once the site is running
>>> and the user removes the install directory.
>>>
>>> Tom
>>>
>>> -----Original Message-----
>>> From: geeklog-devel-bounces at lists.geeklog.net
>>> [mailto:geeklog-devel-bounces at lists.geeklog.net] On Behalf Of Tom
>>> Sent: March-04-12 8:51 AM
>>> To: 'Geeklog Development'
>>> Subject: Re: [geeklog-devel] Geeklog 1.9.0 update
>>>
>>>>> So we really need to get the plugin authors on board for this one.
>>>
>>> I posted this a couple of weeks ago in the mailing list about my
>>> thoughts on
>>> this:
>>>
>>> Geeklog has changed the way it handles topics and how they are
>>> assigned to stories and blocks in 1.9.0. For most plugins this should
>>> not
>> affect them.
>>> While Geeklog 1.9.0 will not be released for a couple of months I
>>> wanted to give the developers a heads up on what has changed.  When
>>> the RC is released I will also be posting this information on
>>> Geeklog.net
>>>
>>> For plugins that create blocks or manipulate blocks within the blocks
>>> table there could be problems. If your plugin supports center blocks
>>> there could also be problems.  Upgrading a Geeklog site to 1.9.0 with
>>> plugins that are currently installed that do this could cause the
>>> site not to function. These plugins should be disabled before
>>> upgrading Geeklog.  I also wonder if we should include a version of
>>> Suprsidr's Geeklog Emergency Rescue Tool along with this release in
>>> case a webmaster has problems. (with Suprsidr permission of course)
>>>
>>> http://www.geeklog.net/article.php/20100222022417548
>>>
>>> Anyways, I am currently modifying the Geeklog Fourm to support
>>> Geeklog 1.9.0. Here is what I have found:
>>>
>>> Since topic assignments for blocks are now stored in the topic
>>> assignment table installing Geeklog 1.9.0 will break the forum (the
>>> forum attempts to use the topic column in the blocks table which does
>>> not exist anymore). The forum has 2 blocks. The forum menu which gets
>>> enabled and disabled and the latest forum posts block. After looking
>>> at the code the best/easiest way to fix this issue while still
>>> supporting Geeklog 1.6.0+ is to make these blocks dynamic. See:
>> http://wiki.geeklog.net/index.php/Dynamic_Blocks.
>>>
>>> The forum also has an issue with the center block. It attempts to
>>> check the stories table to see if it is featured for the current
>>> topic so it knows where to place the forum center block (above or
>>> below the story). This causes a sql error since story topic
>>> assignments are now stored in the topic assignment table. I may
>>> create a new Geeklog plugin function call for this so plugins can get
>>> a true or false answer instead of having the plugin itself querying these
> tables.
>>>
>>> Let me know if you have any questions.
>>>
>>>
>>> -----Original Message-----
>>> From: geeklog-devel-bounces at lists.geeklog.net
>>> [mailto:geeklog-devel-bounces at lists.geeklog.net] On Behalf Of Dirk
>>> Haun
>>> Sent: March-04-12 5:16 AM
>>> To: Geeklog Development
>>> Subject: [geeklog-devel] Geeklog 1.9.0 update
>>>
>>> I have a feeling that the 1.9.0 release will cause a lot of breakage,
>>> especially with plugins. I've been running into all sorts of small
>>> issues all morning .
>>>
>>> For example, the Forum plugin fails to install due to the use of the
> 'tid'
>>> field when adding a block. The MySQLi class is more picky about
>>> things than the old MySQL class, which also seems to affect some
>>> plugins (including the Polls plugin, which did call
>>> mysql_real_escape_string() directly in the plugin upgrade code
> somewhere).
>>>
>>>
>>> So we really need to get the plugin authors on board for this one.
>>>
>>> We also need to make it really clear this time that there may be
>>> issues when trying out early versions - including the risk of the
>>> site no longer working due to plugin incompatibilities.
>>>
>>> Any thoughts on how to best approach this?
>>>
>>> bye, Dirk
>>>
>>>
>>> --
>>> 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
>>
> _______________________________________________
> 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
>