[geeklog-devel] plugin_autoinstall - two more issues
Randy.Kolenko at nextide.ca
Wed Oct 7 07:44:13 EDT 2009
> Plugins should not modify tables they don't own. I don't know of any
> plugins that do. You want to add info to a story or a forum post you
> create a table with a sid or (whatever the forum primary key is) as a
> foreign key and you maintain that table outside the main table.
Really? How could the forum/stories/pluginx possibly use that data then
if the newly insertted data is in a separate table? I'm not trying to
sound snarky here -- just really trying to understand the approach.
> All of those places are the "middle". Middle is anywhere that is not
> before or after. What are you getting at?
Trying to clarify where our understanding of what we're talking about
meets or separates. Trying to understand where you're coming from and
trying to convey where I'm coming from.
> Now you want to add another file that is always included from the
> functions.inc page rather than putting it in existing autoinstall
> file. Does this scale?
May not scale for Geeklog 1.6 -- but if its in its own file, 1.6.x could
include the uninstall ONLY when on the plugins page when the uninstall
is clicked. That scales.
> Wait, why am I talking about scale? What are we talking about? Oh,
> yeah, I wrote a different autoinstaller for plugins that's been in
> use in glFusion for a while. Use it. Don't use it. Look at it for
> ideas. Ignore it. Whatever. I have nothing else to really say about
> it. The code speaks for itself and it's GPL2.
That's great Joe. I looked at it and I simply asked a question as to if
we used that approach, how can we manage external data. That is all.
It was a valid question that I don't have an answer to yet. Perhaps its
my lack of understanding on your approach so I asked for clarification.
More information about the geeklog-devel