Not sure if these following errors are in the works of being fixed.. but,
while editing/saving an existing Article of mine, I recieved the following
errors:
Warning: call_user_func_array() [function.call-user-func-array]: First
argumented is expected to be a valid callback,
spencerp wrote:
Not sure if these following errors are in the works of being fixed.. but,
while editing/saving an existing Article of mine, I recieved the following errors:
Warning: call_user_func_array() [function.call-user-func-array]: First
argumented is expected to be a valid callback,
Matt Mullenweg wrote:
Stefano wrote:
Then before to eliminate it would have been better having a real
alternative to it, i think lof of user use it and with wp-cron plugin
is a real easy way to have people do backup that in other way would be
missed... and removing it without a solution that
On Sep 25, 2006, at 5:38 AM, Ryan Duff wrote:
On a side note, I don't even use the plugin, but am confused to
hell as
to why you would just removed something then give no reason as to why
and no reasoning as to why it shouldn't still be included.
He explained it briefly in the commit:
This
On Sun, 24 Sep 2006 12:19:42 -0700, Matt Mullenweg [EMAIL PROTECTED]
wrote:
Stefano wrote:
Then before to eliminate it would have been better having a real
alternative to it, i think lof of user use it and with wp-cron plugin
is a real easy way to have people do backup that in other way would
On 9/25/06, Stefano [EMAIL PROTECTED] wrote:
On Mon, 25 Sep 2006 07:26:20 -0400, Robert Deaton
[EMAIL PROTECTED] wrote:
On 9/25/06, Stefano [EMAIL PROTECTED] wrote:
Having it included in WP distro made people use it and beeing view not
as a plugin, but as a WP feature, removing it without an
My english written sucks but i can try explain this problem (i can't find
this reported in trac and I assume is not reported) using a example:
This bug is reported in WordPress 2.0.4 and old versions):
When your make title Howto make this? the ? is deleted from slug
(howto-make-this) but the ¿
On Mon, 25 Sep 2006 09:53:16 -0700, Lloyd D Budd
[EMAIL PROTECTED] wrote:
I'm wrong if I say this is only a partial replacement and not a really
alternative solution?
The version in developer (2.1) is just that, in developer. If this
functionality is a priority, then this is an opportunity to
On 9/24/06, Ryan Boren [EMAIL PROTECTED] wrote:
If there are any other changes you think should be ported to 2.0.5,
shout out
Possibly shake out the gzip compression and RTE issue for 2.0.5?
http://trac.wordpress.org/ticket/3144
___
wp-testers
I support this quote, I'm Spanish and I have the same errors in my WP blog.
2006/9/25, Héctor Delcourt (Armonth) [EMAIL PROTECTED]:
My english written sucks but i can try explain this problem (i can't find
this reported in trac and I assume is not reported) using a example:
This bug is
Possibly shake out the gzip compression and RTE issue for 2.0.5?
http://trac.wordpress.org/ticket/3144
Actually I am the one who submitted 3144. That problem is only in 2.1. The
gzip handler for TinyMCE is working fine in 2.0.5.
Jamie Holly
http://www.intoxination.net
We originally included the DB backup plugin because we didn't offer a
proper exporter. Import/export has long been on the to-do but no one
has stepped up. Finally, Matt and some others wrote an exporter and
made it happen. Since the DB backup plugin is currently unmaintained
and since we
On 9/25/06, Stefano [EMAIL PROTECTED] wrote:
On Mon, 25 Sep 2006 07:26:20 -0400, Robert Deaton
[EMAIL PROTECTED] wrote:
On 9/25/06, Stefano [EMAIL PROTECTED] wrote:
Having it included in WP distro made people use it and beeing view not
as a plugin, but as a WP feature, removing it without an
On 9/25/06, Ryan Boren [EMAIL PROTECTED] wrote:
We originally included the DB backup plugin because we didn't offer a
proper exporter. Import/export has long been on the to-do but no one
has stepped up. Finally, Matt and some others wrote an exporter and
made it happen. Since the DB backup
On 9/25/06, Craig [EMAIL PROTECTED] wrote:
On 9/25/06, Joefish [EMAIL PROTECTED] wrote:
The XML export is a nice feature, but as far as I'm concerned, it's
kind of useless. Maybe I'm eyeballing the exported XML wrong, but it
doesn't seem like it makes note of post and comment ID numbers. A
On 9/25/06, Joefish [EMAIL PROTECTED] wrote:
The XML export is a nice feature, but as far as I'm concerned, it's
kind of useless. Maybe I'm eyeballing the exported XML wrong, but it
doesn't seem like it makes note of post and comment ID numbers. A lot
of links are going to break if posts and
I'm still not clear on whether or not the plugin has a security
vulnerability, but anyway - perhaps there is a way to disable the plugin if
it's active, so if people upgrade, it would be disabled? Or is it still a
problem just to have it in your plugins directory?
On 9/25/06, Robert Deaton [EMAIL PROTECTED] wrote:
On 9/25/06, Joefish [EMAIL PROTECTED] wrote:
The XML export is a nice feature, but as far as I'm concerned, it's
kind of useless. Maybe I'm eyeballing the exported XML wrong, but it
doesn't seem like it makes note of post and comment ID
On 9/25/06, Trevor Turk [EMAIL PROTECTED] wrote:
I'm still not clear on whether or not the plugin has a security
vulnerability, snip
Do you honestly think Matt would just up and lie about a security
issue existing?
http://www.google.com/search?q=wordpress+database+backup+plugin+vulnerability
Robert Deaton wrote:
On 9/25/06, Trevor Turk [EMAIL PROTECTED] wrote:
I'm still not clear on whether or not the plugin has a security
vulnerability, snip
Do you honestly think Matt would just up and lie about a security
issue existing?
Robert Deaton wrote:
I think its a good case for leaving it in 2.1 and indefinitely. Like I
said before, even if we put a giant glaring message saying We now
recommend the use of the XML export. Or, although this would never
happen, we could remove it from future versions and supply a seperate
Ryan Duff wrote:
With such a large community, especially those in the coding side, heck,
even the user side... and the way things like this always happen... I'm
amazed that you still just do things, give no reason, then don't even
reason with the users when they complain.
I'm happy to further
Conrad - Conrad_Vanl wrote:
It seems like we're making a big deal about nothing. If there's a security issue with the DB backup then remove it. If people want it they'll download it. I've never even used the DB backup, I've always just used phpMyAdmin for stuff like that ... it's easier (for me
there aren't any current known vulnerabilities with the code that was
removed. -- then what's the big deal about? If there aren’t any
vulnerabilities then what's the big fuss about and why was it removed?
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of
On 9/25/06, Conrad - Conrad_Vanl [EMAIL PROTECTED] wrote:
there aren't any current known vulnerabilities with the code that was removed.
-- then what's the big deal about? If there aren't any vulnerabilities then what's the
big fuss about and why was it removed?
See:
On 9/25/06, Ryan Boren
25 matches
Mail list logo
