Closed GoogleCodeExporter closed 9 years ago
[deleted comment]
[deleted comment]
Hey Danny,
we could integrate some code to detect plugins, but .. which plugins should we
detect? In addition .. I already ran into a situation where a plugin author did
a
complete rewrite of the plugin so I had to rewrite my detection. Took me a
while to
figure out why my old detection stopped working.
What if the author extends the plugins CSS?
Again .. the integration is easy .. but I don't know how we could support a
list of
30+ plugins / widgets?
Cheers,
Chris .. finally back from the snowy mountain ;-)
Original comment by chris.gossmann@googlemail.com
on 30 Jan 2009 at 3:07
You are right. I didn't think about that. I think the solution might be the
following: in my child themes, I usually customize some widgets (as last fm,
wp125
and more) with some css codeaccording to my theme. if the plugin changes (as you
wrote before) I would like to inform the user that MAYBE the widget display
might be
different. in this unfortunate case, he/she will be adviced to deactivate the
plugin
or ask for a new customization according to the new release. when we install a
plugin, we could trace the name and version in the DB. once the name will become
different, a warning message may appear when the admin log in.
what do you think?
by the way: welcome back!
Original comment by dannydam...@gmail.com
on 30 Jan 2009 at 4:44
Original comment by ian%them...@gtempaccount.com
on 22 Feb 2009 at 11:05
Original issue reported on code.google.com by
dannydam...@gmail.com
on 25 Jan 2009 at 2:38