1 sam2kb Apr 30, 2008 23:16
3 edb May 02, 2008 09:26
Maybe no one replied because no one has a reply to give? Or possibly no one who might know about it (and do something about it) pays any attention to bugs in the 1.* generation any more? Somewhat obsolete unless a security hole is discovered yah?
Good catch though. I suppose I should tweak my remaining 1.10.3 installation to reflect this fix - not that I need it given that I have no plugins that need to access the plugin folder from the front end. Still it's nice to keep my files as functional as possible ;)
4 sam2kb May 02, 2008 09:41
I don't actually care about 1.x generation, but I have to finish my plugin and at the same time don't kill all others with this "fix".
Please try it when you get a chance.
5 edb May 02, 2008 10:04
Okay will do, but it won't be soon due to I really want to finish a plugin translation maker plugin.
6 sam2kb May 02, 2008 10:06
No problem, it's already work well with $base = $plugins_url;
Since nobody replies I guess this is not a bug. But why it does this thing, any ideas?
This part $Blog->get('baseurl') is gone in 2.x version