[geeklog-devel] Dynamic Blocks on Blocks Admin Page

[Trinity]

if i remember right the current dynamic blocks plug in piece was written by
me and then expanded by the forum plug in creator because at the time he
used a hack to do his that wasn't available to other plugins.  the intent
was to make this avaliable to all plugins and eventaly replace adding
plugin derived blocks to the blocks table leaving them to custom user based
blocks exclusively. bear in mind its been a long time since i worked on
geeklog code so i am not aware of the current status of the code in
question or whether its still relevent to current develpment goals.

On Mon, Mar 19, 2012 at 8:56 AM, Tom <websitemaster at cogeco.net> wrote:

> >> They were created for the forum plugin because Blaine wanted the forum
> menu to always be at the top of the block list.
>
> The funny thing is the forum plugin didn't use it until now.
>
> >> Wouldn't it make more sense to merge the dynamic blocks with the
> database?
>
> The only real argument I see is it would make the admin lists easier (it
> will be hard to combine a data array with db info since the function allows
> searching, paging, etc.. unless we tone down the features available to the
> list if an array and db data is used).
>
> 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: March-18-12 8:55 PM
> To: Geeklog Development
> Subject: Re: [geeklog-devel] Dynamic Blocks on Blocks Admin Page
>
> > Not for the next (2.0) release, but I think it would make a good
> > feature request to upgrade the Admin List function to merge the
> > database blocks with dynamic blocks. It shouldn't be too hard to do,
> > though again targeting the next release.
>
> Wouldn't it make more sense to merge the dynamic blocks with the database?
> In other words, dynamic blocks need some kind of entry in the database or
> they don't exist. It's probably not much of code change for the few plugins
> that use dynamic blocks and simplifies the code in the admin screen.
> Arguably, dynamic blocks are not needed. They were created for the forum
> plugin because Blaine wanted the forum menu to always be at the top of the
> block list. There's no good reason why the forum menu plugin isn't a P HP
> block that checks to see if the page is a forum page before outputing the
> menu.
>
> _______________________________________________
> 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: <https://pairlist8.pair.net/pipermail/geeklog-devel/attachments/20120319/35555b61/attachment.html>