Nabble - Wordpress Hackers

Re: (Another) problem with WP_Rewrite - The too-many-pages-bug

2009-11-24T21:09:05Z

Actually, that is part of the WordPress WP_Rewrite feature. It allows
for easily finding paths that are completely dynamic.

For example, most web sites would have that hard coded into the
controller, but since WordPress allows for customizing the rewrite rules
to the extreme, it would be almost impossible to allow for the extension
using my code. Therefore, I mean, I would allow you to use the hard
coded rewrites, if you wish and probably set up a few of them to use
them, since it is the same as in WordPress. It is just that with
postnames, it would be too slow to do all of the queries needed to get
what you were looking at otherwise.

Not really scalable when you get up to the tens of thousands or for some
just thousands of posts. So, what I'm trying to say, is that it wouldn't
be fixed with my rewrite of the WP_Rewrite and WP_Query components.

Jacob Santos

Daniel Dvorkin wrote:

> Hi,
>
> I stumbled across this bug: http://core.trac.wordpress.org/ticket/10798
> It's really messy.
>
> Changing the $use_verbose_page_rules to false in the WP_rewrite class,
> seems to solve the problem... In fact, everything that I checked works
> fine now.
>
> But I need to understand what else modifies that change... and I can't
> find any information...
>
>
> Thanks!
> _______________________________________________
> wp-hackers mailing list
> wp-hackers@...
> http://lists.automattic.com/mailman/listinfo/wp-hackers
>

_______________________________________________
wp-hackers mailing list
wp-hackers@...
http://lists.automattic.com/mailman/listinfo/wp-hackers

(Another) problem with WP_Rewrite - The too-many-pages-bug

2009-11-24T18:24:17Z

Hi,

I stumbled across this bug: http://core.trac.wordpress.org/ticket/10798
It's really messy.

Changing the $use_verbose_page_rules to false in the WP_rewrite class,
seems to solve the problem... In fact, everything that I checked works
fine now.

But I need to understand what else modifies that change... and I can't
find any information...

Thanks!
_______________________________________________
wp-hackers mailing list
wp-hackers@...
http://lists.automattic.com/mailman/listinfo/wp-hackers

The problem with WP_Rewrite <<< RE: Options for Controller - Views

2009-11-24T16:56:33Z

My main problem with wanting to rewrite it and I apologize for going off
on a tangent, is that I shouldn't have to think and test as much as I do
when working with WP_Rewrite. I shouldn't have to do all sorts of calls
to functions to set up a rewrite when all I need to do is use one hook.
Why do I have to use the long way, when I can just use the shortcut
named template_redirect.

My point is why even have all of that code when you have to use
template_redirect anyway.

You are telling me and actually believe that it is an excellent idea,
which I can't understand, that I can either spend hours going through
and using WP_Rewrite just to have to use template_redirect. You are
basically telling me that my only advantage is that I won't get the 404
title when WP_Query parses the query vars and determines that the page
doesn't exist.

So the option is spend four hours on just getting WP_Rewrite to work,
and then another 10 to 30 minutes to get template_redirect working with
the query_vars.

OR

I can spend an extra 20 minutes doing my own regex or request_uri
parsing. Yeah, sure, the only advantage I'll get is that my
template_redirect won't make you cringe when you look at it.

I think the high learning curve is driving many people away. It doesn't
work like you would assume it will work and requires a lot of extra work
that has to be done exactly right in order to work correctly.

What I'm talking about is a single function which is it, one single
function that can be called anywhere and will bypass WP_Query
completely. WP_Query will use the new system, thus giving a better idea
and an example of how plugin developers should be doing it. I'm talking
about a clear and easy API which is not so tightly integrated in to
WordPress that you need to bypass WordPress after WordPress has already
processed everything in order to do what you wanted.

Now, sure, I'll give you that once I am able to get the WP_Rewrite
working once and understand what is going on, it will take a lot less
time, but it doesn't work as many of the other controllers
implementations out there do. I think that it is incomplete, everything
right now was written not to allow for extension, but to allow for
WordPress to kind of have a sort of front controller implementation.

It is actually quite impressive for its time, but that was years ago and
I think it is time for a little bit change. Yeah, sure it works and has
been working for a long, long time with minor or no issues, but I want
to change that. I want to rewrite a tiny and critical subset of
WordPress that will have bugs, features that people won't need and may
not use for a long time. I will do this, because it suits my needs and I
want to manage another component for some time before it gets passed off
to anyone who will manage it after me.

I mean, it will probably be 6 months to a year before it is reviewed for
inclusion in to WordPress. Also, it might be useful to someone who
wishes to take my idea in the future and apply it to WordPress and
hopefully is capable enough to not include bugs or fix the ones in my
implementation.

I should have left a note saying that I won't be able to do this for
another 2 weeks at least. I keep thinking about doing this, but it is
time consuming and before I was doing it for WordPress and I was unsure
if any of the ones with commit access would commit it. I didn't want to
spend the weeks writing it and then take the risk of it not being
committed. Now that I'm doing it for me, I'm less concerned about that.
I'm saying it might be soon or it might not, but I wanted to know what
everyone else would like the direction to be.

Jacob Santos
_______________________________________________
wp-hackers mailing list
wp-hackers@...
http://lists.automattic.com/mailman/listinfo/wp-hackers

Re: comments_number() function renames first parameter

2009-11-24T14:31:58Z

Ok, Nevermind - it looks like Intense Debate was overriding my functions -
everyone can go about your business - thanks!

On Tue, Nov 24, 2009 at 4:22 PM, Tim Schoffelman <tim@...> wrote:

> Also, I'm running the Intense Debate plugin (latest version), which now
> that I'm thinking about it, may be the issue - checking...
>
>
>
>
> On Tue, Nov 24, 2009 at 4:21 PM, Tim Schoffelman <tim@...>wrote:
>
>> Hey Everyone,
>>
>> Running into a interesting situation to which I can't find any
>> documentation in the codex on it.
>>
>> I want to display the number of comments for each post using either the
>>
>> <?php comments_number(__('comment',"blogname"), __('1 comment',
>> "blogname"), __('% comments', "blogname")); ?>
>>
>> or the
>>
>> <?php comments_popup_link(__('comment', "blogname"), __('1 comment',
>> "blogname"), __('% comments', "blogname")); ?>
>>
>> functions.
>>
>> The problem is that when the page is loading it displays "comment" (which
>> I want) if I have zero comments, but one of the last things that it does is
>> right before it's finished loading the page, "comment" changes to "Comments
>> (0)". It doesn't matter if I take out the localization either.
>>
>> Also, I'm running WordPress MU 2.8.4a
>>
>> Any thoughts?
>>
>> Thanks!
>> Tim Schoffelman
>>
>
>

_______________________________________________
wp-hackers mailing list
wp-hackers@...
http://lists.automattic.com/mailman/listinfo/wp-hackers

Re: comments_number() function renames first parameter

2009-11-24T14:22:47Z

Also, I'm running the Intense Debate plugin (latest version), which now that
I'm thinking about it, may be the issue - checking...

On Tue, Nov 24, 2009 at 4:21 PM, Tim Schoffelman <tim@...> wrote:

> Hey Everyone,
>
> Running into a interesting situation to which I can't find any
> documentation in the codex on it.
>
> I want to display the number of comments for each post using either the
>
> <?php comments_number(__('comment',"blogname"), __('1 comment',
> "blogname"), __('% comments', "blogname")); ?>
>
> or the
>
> <?php comments_popup_link(__('comment', "blogname"), __('1 comment',
> "blogname"), __('% comments', "blogname")); ?>
>
> functions.
>
> The problem is that when the page is loading it displays "comment" (which I
> want) if I have zero comments, but one of the last things that it does is
> right before it's finished loading the page, "comment" changes to "Comments
> (0)". It doesn't matter if I take out the localization either.
>
> Also, I'm running WordPress MU 2.8.4a
>
> Any thoughts?
>
> Thanks!
> Tim Schoffelman
>

_______________________________________________
wp-hackers mailing list
wp-hackers@...
http://lists.automattic.com/mailman/listinfo/wp-hackers

comments_number() function renames first parameter

2009-11-24T14:21:39Z

Hey Everyone,

Running into a interesting situation to which I can't find any documentation
in the codex on it.

I want to display the number of comments for each post using either the

<?php comments_number(__('comment',"blogname"), __('1 comment', "blogname"),
__('% comments', "blogname")); ?>

or the

<?php comments_popup_link(__('comment', "blogname"), __('1 comment',
"blogname"), __('% comments', "blogname")); ?>

functions.

The problem is that when the page is loading it displays "comment" (which I
want) if I have zero comments, but one of the last things that it does is
right before it's finished loading the page, "comment" changes to "Comments
(0)". It doesn't matter if I take out the localization either.

Also, I'm running WordPress MU 2.8.4a

Any thoughts?

Thanks!
Tim Schoffelman
_______________________________________________
wp-hackers mailing list
wp-hackers@...
http://lists.automattic.com/mailman/listinfo/wp-hackers

Re: WP as a CMS with a touch of Blogging

2009-11-24T11:55:17Z

>> Owen Winkler's redirectify is the simplest. (sadly no longer available
>> but
>> email me privately and I'll send you a copy.)
>
>
> Mike,
>
> If the plugin still works, is open source, and isn't in the Plugin DB,
> consider cleaning it up, crediting the original author, and publishing
> it there - especially if Owen doesn't want to mess with it anymore.

I stumbled across this thread and wanted to mention that I've just
uploaded my redirect plugin bbRedirector today. It should be available
shortly (just committed the first version to svn).

I've created it some time ago for a client and finally had some time to
clean it up and share it with the rest of the world. Perhaps it is
helpful for you.

See:
http://wordpress.org/extend/plugins/bbredirector/

--

met vriendelijke groet,
Bjorn Wijers

* b u r o b j o r n .nl *
digitaal vakmanschap | digital craftsmanship

Concordiastraat 68-126
3551 EM Utrecht
The Netherlands

phone: +31 6 49 74 78 70
http://www.burobjorn.nl
_______________________________________________
wp-hackers mailing list
wp-hackers@...
http://lists.automattic.com/mailman/listinfo/wp-hackers

Re: Changing the maintenance mode text

2009-11-23T19:16:49Z

Thanks to both of you. I had seen the first part which is how I found out
about the .maintenance file to begin with but my eyes completely overlooked
the part 2 link.

Robert Pendell
shinji@...
CAcert Assurer
"A perfect world is one of chaos."
_______________________________________________
wp-hackers mailing list
wp-hackers@...
http://lists.automattic.com/mailman/listinfo/wp-hackers

Re: Changing the maintenance mode text

2009-11-23T17:58:33Z

> Is there anyway to change the maintenance mode text displayed without
> using a plugin?
>
> Robert Pendell

Sure is, but instead of explaining it all here, howsabout I point you in the
direction of Matt's page on it?

http://sivel.net/2009/06/wordpress-maintenance-mode-without-a-plugin/

--
Mark Waterous
http://mark.watero.us/
(mark@...)

_______________________________________________
wp-hackers mailing list
wp-hackers@...
http://lists.automattic.com/mailman/listinfo/wp-hackers

Re: Changing the maintenance mode text

2009-11-23T17:39:40Z

> Is there anyway to change the maintenance mode text displayed without using
> a plugin?

Take a look at http://sivel.net/2009/06/wordpress-maintenance-mode-without-a-plugin-part-2/

--
Matt Martz
matt@...
http://sivel.net/
_______________________________________________
wp-hackers mailing list
wp-hackers@...
http://lists.automattic.com/mailman/listinfo/wp-hackers

Changing the maintenance mode text

2009-11-23T17:37:45Z

Is there anyway to change the maintenance mode text displayed without using
a plugin?

Robert Pendell
shinji@...
CAcert Assurer
"A perfect world is one of chaos."
_______________________________________________
wp-hackers mailing list
wp-hackers@...
http://lists.automattic.com/mailman/listinfo/wp-hackers

Re: Options for Controller - Views

2009-11-23T15:17:13Z

I still don't understand the problem, exactly. It seems perfectly
clear and separated to me. I think you're conflating what each piece
does and trying to make things do something they were never designed
to do.

It's really quite simple.

URL comes in, gets grabbed.
WP_Rewrite parses it, sets up query_vars.
WP_Query is loaded and uses query_vars to get database data. Also sets
some internal flags.
template-loader.php is loaded last, and uses those flags to determine
the correct view.

Where is the disconnect between these? WP_Rewrite is relatively easy
to adjust and change if you know regexp. WP_Query is less easy to
change, but often it's unnecessary to mess with if you're loading
custom data. And the template-loader couldn't really be any more
simple, though it probably could be more efficient.

Let's try another approach: What is it that you want to do that you're
finding very difficult to do? Because I think you're simply
doing-it-wrong, somehow. If you want to "replace" WordPress' control,
than that's really not at all difficult to do.

-Otto
Sent from Memphis, TN, United States

On Fri, Nov 20, 2009 at 4:02 PM, Jacob Santos <wordpress@...> wrote:

> Okay, so looking at the issue, it seems I had thought that the WP_Query was
> the router, but really it is WP_Rewrite. Also, it seems that too much is
> really just tied to WordPress itself and requires work to extend with other
> uses. In my opinion, WP_Rewrite and WP_Query can exist, but new code can be
> created for WordPress that is more generic that the two classes can then
> use.
>
> In this way, the Router, URI, and Controller can be separated in to their
> own easily identified components. The Views can also be changed to not be
> based off of the template loader file.
>
> I believe the problem is that too much of the code is affecting WordPress
> and it is difficult to see how to work within the parameters to add and
> change. In this way the entire set up is really a hack provided to allow for
> other people to extend WordPress but not really take it and replace
> WordPress cleanly.
>
> Part of the issue is lack of documentation and well, if no one is going to
> step up that knows it well enough (I can't get the code to work that is on
> the Codex) then really, when I write the new code, I'll be sure to write out
> a detailed explanation.
>
> You know if someone wants to help, I can create a ticket and apply the
> patches when I have something. Or if someone wants to take it in a new
> direction, I think, if there are multiple implementations then the best one
> can be looked at. (Also I will probably "steal" it for my own project.)
>
> Jacob Santos
> _______________________________________________
> wp-hackers mailing list
> wp-hackers@...
> http://lists.automattic.com/mailman/listinfo/wp-hackers
>

_______________________________________________
wp-hackers mailing list
wp-hackers@...
http://lists.automattic.com/mailman/listinfo/wp-hackers

WordPress dev chat will not be happening this week.

2009-11-23T14:42:07Z

Hi All,

Just a heads up for those of you who are interested.

The next dev chat will be on Thursday 3rd December at the usual time
of 9PM UTC.

This weeks is skipped due to Thanksgiving.

As usual agenda items can be suggested here: http://wpdevel.wordpress.com/

Thanks

Westi
--
Peter Westwood
http://blog.ftwr.co.uk | http://westi.wordpress.com
C53C F8FC 8796 8508 88D6 C950 54F4 5DCD A834 01C5

_______________________________________________
wp-hackers mailing list
wp-hackers@...
http://lists.automattic.com/mailman/listinfo/wp-hackers

Re: Multilanguage Support in 2.9rare

2009-11-23T07:37:36Z

Hello Peter,

thanks for your reply, works fine with fr_FR, not with de_DE.
I will see for this problem on the german team.
Thanks a lot

http://inpsyde.com
http://pressthis.de

On Sun, Nov 22, 2009 at 3:51 PM, Peter Westwood
<peter.westwood@...> wrote:

>
> On 20 Nov 2009, at 08:25, Frank Bueltge wrote:
>
>> with the last update before 2 days and today on the nightly build it
>> is not possiblt to use a other language. Do you have an idea?
>> I have install the language-folder in wp-content with the
>> languages-files (de_DE) and have also set the constant in the
>> wp-config.php
>>
>> Also, all plugins dosnt work with other language. The same problem is
>> on my dev-area on local machine.
>>
>
> I have just tested this on trunk (with fr_FR.mo) and it all appears to work.
>
> Is it still not working for you?
>
> Cheers
> --
> Peter Westwood
> http://blog.ftwr.co.uk | http://westi.wordpress.com
> C53C F8FC 8796 8508 88D6 C950 54F4 5DCD A834 01C5
>
> _______________________________________________
> wp-hackers mailing list
> wp-hackers@...
> http://lists.automattic.com/mailman/listinfo/wp-hackers
>

_______________________________________________
wp-hackers mailing list
wp-hackers@...
http://lists.automattic.com/mailman/listinfo/wp-hackers

Re: Update post status

2009-11-22T21:29:14Z

>
> What I'm looking to do is trigger the correct function when the STATUS
> changes. Like I said - when I update the post from DRAFT to FUTURE, is
> there
> something more to do than set the status to FUTURE, and make sure the date
> is in the future?
>
>
You can use the action transition_post_status. Or if you want to trigger
only on specific status changes (i.e. to take action only when a post DRAFT
to FUTURE/PUBLISH) use ${old_status}_to_$new_status.

Details here: http://codex.wordpress.org/Post_Status_Transitions

--
Mo Jangda
www.digitalize.ca | @mjangda
_______________________________________________
wp-hackers mailing list
wp-hackers@...
http://lists.automattic.com/mailman/listinfo/wp-hackers

Re: Update post status

2009-11-22T21:04:15Z

Thanks Russ Gilbert for the reply regarding the wp_update_post function but
it isn't exactly what I was after, although that is the correct way to
update the post's information.

What I'm looking to do is trigger the correct function when the STATUS
changes. Like I said - when I update the post from DRAFT to FUTURE, is there
something more to do than set the status to FUTURE, and make sure the date
is in the future?

--
Jeff Rose
------------------
http://www.twitter.com/JeffRose
http://www.linkedin.com/in/JeffeRose
http://www.installedforyou.com
_______________________________________________
wp-hackers mailing list
wp-hackers@...
http://lists.automattic.com/mailman/listinfo/wp-hackers

Re: Change Password on Wordpress Plugins

2009-11-22T11:48:16Z

On Sun, Nov 22, 2009 at 5:12 PM, Oliver Schlöbe <office@...> wrote:
> Go here: http://wordpress.org/support/, log in, then click "View your
> profile", then "Edit" on the right-hand side. Et voilà. There you are.
>
>
> On 22.11.2009 19:59, Vinicius Massuchetto wrote:
>>
>> I know it sounds stupid, but I couldn't find any "change password"
>> section on my account on http://wordpress.org/extend/plugins/.
>> Is this option available?

Nice! Thanks to all of you.

As I subscribed to submit a plugin, the first place I clicked was on
my nickname on the right. The "view your profile" is not shown on
http://wordpress.org/extend/plugins/.

I guess the same link would be useful there.

Thanks again.
--
Vinícius Massuchetto
_______________________________________________
wp-hackers mailing list
wp-hackers@...
http://lists.automattic.com/mailman/listinfo/wp-hackers

Re: Change Password on Wordpress Plugins

2009-11-22T11:12:50Z

Go here: http://wordpress.org/support/, log in, then click "View your
profile", then "Edit" on the right-hand side. Et voilà. There you are.

On 22.11.2009 19:59, Vinicius Massuchetto wrote:

> I know it sounds stupid, but I couldn't find any "change password"
> section on my account on http://wordpress.org/extend/plugins/.
> Is this option available?
>
> Thanks.
> --
> VinÃcius Massuchetto
> http://vinicius.soylocoporti.org.br
> _______________________________________________
> wp-hackers mailing list
> wp-hackers@...
> http://lists.automattic.com/mailman/listinfo/wp-hackers
>

--
Regards,
Oliver Schlöbe

http://wpseek.com/
http://wpworldmap.net/

_______________________________________________
wp-hackers mailing list
wp-hackers@...
http://lists.automattic.com/mailman/listinfo/wp-hackers

Re: Change Password on Wordpress Plugins

2009-11-22T11:04:08Z

you have to go to your profile on the Forum.... dont ask me why...

On Sun, Nov 22, 2009 at 4:59 PM, Vinicius Massuchetto <
viniciusandre@...> wrote:

> I know it sounds stupid, but I couldn't find any "change password"
> section on my account on http://wordpress.org/extend/plugins/.
> Is this option available?
>
> Thanks.
> --
> Vinícius Massuchetto
> http://vinicius.soylocoporti.org.br
> _______________________________________________
> wp-hackers mailing list
> wp-hackers@...
> http://lists.automattic.com/mailman/listinfo/wp-hackers
>

--
leogermani.pirex.com.br
leogermani.estudiolivre.org
_______________________________________________
wp-hackers mailing list
wp-hackers@...
http://lists.automattic.com/mailman/listinfo/wp-hackers

Re: Change Password on Wordpress Plugins

2009-11-22T11:03:54Z

On 22 Nov 2009, at 18:59, Vinicius Massuchetto wrote:

> I know it sounds stupid, but I couldn't find any "change password"
> section on my account on http://wordpress.org/extend/plugins/.
> Is this option available?
>

Navigate to the Support forums and go to your profile there where you
can then change your password.

You have one username and password for everything on WordPress.org

Cheers
--
Peter Westwood
http://blog.ftwr.co.uk | http://westi.wordpress.com
C53C F8FC 8796 8508 88D6 C950 54F4 5DCD A834 01C5

_______________________________________________
wp-hackers mailing list
wp-hackers@...
http://lists.automattic.com/mailman/listinfo/wp-hackers

Re: Change Password on Wordpress Plugins

2009-11-22T11:03:35Z

Visit http://wordpress.org/support/ and then click View Your profile and now
click Edit on right and find password change section at the bottom.

-
Navjot Singh

On Mon, Nov 23, 2009 at 12:29 AM, Vinicius Massuchetto <
viniciusandre@...> wrote:

> I know it sounds stupid, but I couldn't find any "change password"
> section on my account on http://wordpress.org/extend/plugins/.
> Is this option available?
>
> Thanks.
> --
> Vinícius Massuchetto
> http://vinicius.soylocoporti.org.br
> _______________________________________________
> wp-hackers mailing list
> wp-hackers@...
> http://lists.automattic.com/mailman/listinfo/wp-hackers
>

_______________________________________________
wp-hackers mailing list
wp-hackers@...
http://lists.automattic.com/mailman/listinfo/wp-hackers

Change Password on Wordpress Plugins

2009-11-22T10:59:38Z

I know it sounds stupid, but I couldn't find any "change password"
section on my account on http://wordpress.org/extend/plugins/.
Is this option available?

Thanks.
--
Vinícius Massuchetto
http://vinicius.soylocoporti.org.br
_______________________________________________
wp-hackers mailing list
wp-hackers@...
http://lists.automattic.com/mailman/listinfo/wp-hackers

Re: detecting type of edit for parent_save_pre

2009-11-22T08:53:58Z

Thanks, good tip. I guess this would skip Quick Edits too though?

I've started another thread about the problems with that - for now
I've actually disabled Quick Edit for pages where I've locked the
slug. It's tempting to use DOING_AJAX to filter autosaves as it
currently makes no difference, but I'll have to come up with something
more specific if/when I solve the Quick Edit issue.

2009/11/21 Dion Hulse (dd32) <wordpress@...>:

> checking for DOING_AJAX is the simplest way to avoid autosaves for a start
>
> On Sun, 22 Nov 2009 05:29:10 +1100, Steve Taylor <steve@...>
> wrote:
>
>> Just tried this but ran into all sorts of trouble. To be honest I've
>> lost track of what it was - I think it (or I) got confused about
>> revisions being saved.
>>
>> In any case, I've fixed the original problem by detecting
>> $_POST["attachments"] - it works, at least. I'll put the new, more
>> serious issue in a new thread.... Bah.
>>
>>
>> 2009/11/20 scribu <scribu@...>:
>>>
>>> You should hook into 'save_post' instead and check by $post->post_type
>>> instead of relying on the $_POST variable.
>>>
>>>
>>> --
>>> http://scribu.net
>>> _______________________________________________
>>> wp-hackers mailing list
>>> wp-hackers@...
>>> http://lists.automattic.com/mailman/listinfo/wp-hackers
>>>
>> _______________________________________________
>> wp-hackers mailing list
>> wp-hackers@...
>> http://lists.automattic.com/mailman/listinfo/wp-hackers
>>
>
>
> --
> Using Opera's revolutionary e-mail client: http://www.opera.com/mail/
> _______________________________________________
> wp-hackers mailing list
> wp-hackers@...
> http://lists.automattic.com/mailman/listinfo/wp-hackers
>

_______________________________________________
wp-hackers mailing list
wp-hackers@...
http://lists.automattic.com/mailman/listinfo/wp-hackers

Re: Multilanguage Support in 2.9rare

2009-11-22T06:51:18Z

On 20 Nov 2009, at 08:25, Frank Bueltge wrote:

> with the last update before 2 days and today on the nightly build it
> is not possiblt to use a other language. Do you have an idea?
> I have install the language-folder in wp-content with the
> languages-files (de_DE) and have also set the constant in the
> wp-config.php
>
> Also, all plugins dosnt work with other language. The same problem is
> on my dev-area on local machine.
>

I have just tested this on trunk (with fr_FR.mo) and it all appears to
work.

Is it still not working for you?

Cheers
--
Peter Westwood
http://blog.ftwr.co.uk | http://westi.wordpress.com
C53C F8FC 8796 8508 88D6 C950 54F4 5DCD A834 01C5

_______________________________________________
wp-hackers mailing list
wp-hackers@...
http://lists.automattic.com/mailman/listinfo/wp-hackers

Re: detecting type of edit for parent_save_pre

2009-11-21T14:07:00Z

checking for DOING_AJAX is the simplest way to avoid autosaves for a start

On Sun, 22 Nov 2009 05:29:10 +1100, Steve Taylor <steve@...>
wrote:

> Just tried this but ran into all sorts of trouble. To be honest I've
> lost track of what it was - I think it (or I) got confused about
> revisions being saved.
>
> In any case, I've fixed the original problem by detecting
> $_POST["attachments"] - it works, at least. I'll put the new, more
> serious issue in a new thread.... Bah.
>
>
> 2009/11/20 scribu <scribu@...>:
>> You should hook into 'save_post' instead and check by $post->post_type
>> instead of relying on the $_POST variable.
>>
>>
>> --
>> http://scribu.net
>> _______________________________________________
>> wp-hackers mailing list
>> wp-hackers@...
>> http://lists.automattic.com/mailman/listinfo/wp-hackers
>>
> _______________________________________________
> wp-hackers mailing list
> wp-hackers@...
> http://lists.automattic.com/mailman/listinfo/wp-hackers
>

--
Using Opera's revolutionary e-mail client: http://www.opera.com/mail/
_______________________________________________
wp-hackers mailing list
wp-hackers@...
http://lists.automattic.com/mailman/listinfo/wp-hackers

Re: Renaming a plugin

2009-11-21T13:35:33Z

On Nov 21, 2009, at 4:17 PM, Tuna Can wrote:

> Oops! Sorry about that... looks like I have a little egg on my face. :)

No need to apologize, I think it's a good the hackers list is willing to rehash basic stuff.

It hadn't occurred to me that updating readme.txt would also update the plugin name on extend, but that makes sense.

-Dan

>
> --- On Sat, 11/21/09, Dan Phiffer <dan@...> wrote:
>
>> From: Dan Phiffer <dan@...>
>> Subject: Re: [wp-hackers] Renaming a plugin
>> To: wp-hackers@...
>> Received: Saturday, November 21, 2009, 1:14 PM
>>
>> On Nov 21, 2009, at 3:26 PM, mark waterous wrote:
>>
>>> As for changing the name of your plugin within the
>> repository, I don't
>>> believe you can - once a repository is set up it's
>> relatively permanent.
>>
>> Thanks, this was what I was after.
>>
>> -Dan
>> _______________________________________________
>> wp-hackers mailing list
>> wp-hackers@...
>> http://lists.automattic.com/mailman/listinfo/wp-hackers
>>
>
>
> __________________________________________________________________
> Yahoo! Canada Toolbar: Search from anywhere on the web, and bookmark your favourite sites. Download it now
> http://ca.toolbar.yahoo.com.
>
> _______________________________________________
> wp-hackers mailing list
> wp-hackers@...
> http://lists.automattic.com/mailman/listinfo/wp-hackers

_______________________________________________
wp-hackers mailing list
wp-hackers@...
http://lists.automattic.com/mailman/listinfo/wp-hackers

Re: Renaming a plugin

2009-11-21T13:17:26Z

Oops! Sorry about that... looks like I have a little egg on my face. :)

Carry on here... nothing to see... nothing to see... *embarrassed*

Thanks,

Tony

--- On Sat, 11/21/09, Dan Phiffer <dan@...> wrote:

> From: Dan Phiffer <dan@...>
> Subject: Re: [wp-hackers] Renaming a plugin
> To: wp-hackers@...
> Received: Saturday, November 21, 2009, 1:14 PM
>
> On Nov 21, 2009, at 3:26 PM, mark waterous wrote:
>
> > As for changing the name of your plugin within the
> repository, I don't
> > believe you can - once a repository is set up it's
> relatively permanent.
>
> Thanks, this was what I was after.
>
> -Dan
> _______________________________________________
> wp-hackers mailing list
> wp-hackers@...
> http://lists.automattic.com/mailman/listinfo/wp-hackers
>

__________________________________________________________________
Yahoo! Canada Toolbar: Search from anywhere on the web, and bookmark your favourite sites. Download it now
http://ca.toolbar.yahoo.com.

_______________________________________________
wp-hackers mailing list
wp-hackers@...
http://lists.automattic.com/mailman/listinfo/wp-hackers

Re: Renaming a plugin

2009-11-21T13:14:45Z

On Nov 21, 2009, at 3:26 PM, mark waterous wrote:

> As for changing the name of your plugin within the repository, I don't
> believe you can - once a repository is set up it's relatively permanent.

Thanks, this was what I was after.

-Dan
_______________________________________________
wp-hackers mailing list
wp-hackers@...
http://lists.automattic.com/mailman/listinfo/wp-hackers

Re: Renaming a plugin

2009-11-21T12:26:26Z

> Checkout the WordPress Codex page here:
>
> http://codex.wordpress.org/Writing_a_Plugin

I think he might be referring to the information that's displayed on the
repository page for the plugin, in which case he would probably want to take
a look at the readme file information and standards located here:

http://wordpress.org/extend/plugins/about/#readme

As for changing the name of your plugin within the repository, I don't
believe you can - once a repository is set up it's relatively permanent. If
you wanted to change the name of your plugin you would have to request a new
repository be set up under the new name.

--
Mark Waterous
http://mark.watero.us/
(mark@...)

_______________________________________________
wp-hackers mailing list
wp-hackers@...
http://lists.automattic.com/mailman/listinfo/wp-hackers

Re: Renaming a plugin

2009-11-21T12:08:07Z

Checkout the WordPress Codex page here:

http://codex.wordpress.org/Writing_a_Plugin

It will tell you how "the top of your Plugin's main PHP file must contain a standard Plugin information header." The info you want to change is in there.

<?php
/*
Plugin Name: Name Of The Plugin
Plugin URI: http://URI_Of_Page_Describing_Plugin_and_Updates
Description: A brief description of the Plugin.
Version: The Plugin's Version Number, e.g.: 1.0
Author: Name Of The Plugin Author
Author URI: http://URI_Of_The_Plugin_Author
*/
?>

--- On Sat, 11/21/09, Dan Phiffer <dan@...> wrote:

> From: Dan Phiffer <dan@...>
> Subject: [wp-hackers] Renaming a plugin
> To: wp-hackers@...
> Received: Saturday, November 21, 2009, 11:37 AM
> Hi all,
>
> I'm pretty new to WordPress plugin development, so
> apologies if this is an obvious question. How does one go
> about renaming a plugin? Both as in changing the text that
> appears above Description / Installation / Screenshots etc.
> and also the path http://wordpress.org/extend/plugins/[plugin-name]/
>
> Thanks!
> -Dan
> _______________________________________________
> wp-hackers mailing list
> wp-hackers@...
> http://lists.automattic.com/mailman/listinfo/wp-hackers
>

__________________________________________________________________
Looking for the perfect gift? Give the gift of Flickr!

http://www.flickr.com/gift/

_______________________________________________
wp-hackers mailing list
wp-hackers@...
http://lists.automattic.com/mailman/listinfo/wp-hackers

Renaming a plugin

2009-11-21T11:37:39Z

Hi all,

I'm pretty new to WordPress plugin development, so apologies if this is an obvious question. How does one go about renaming a plugin? Both as in changing the text that appears above Description / Installation / Screenshots etc. and also the path http://wordpress.org/extend/plugins/[plugin-name]/

Thanks!
-Dan
_______________________________________________
wp-hackers mailing list
wp-hackers@...
http://lists.automattic.com/mailman/listinfo/wp-hackers

altering the Quick Edit box

2009-11-21T10:38:26Z

I've searched a lot on this issue, but all I can find is other people
stuck on it. Basically, I'm trying to add fields to the Quick Edit box
for pages.

A plugin I'm working on
(http://wordpress.org/extend/plugins/lock-pages/) tries to lock the
editing of specified pages' parent and slug. It works fine on the
normal page edit screen - it stores the old values in hidden fields,
and reverts to them if the user is barred from editing them.

But Quick Edits slip right past this. I got as far as working this out:

- The Quick Edits are each generated dynamically from a hidden
"template" at the bottom of the page
- Each row has a hidden div, which contains a div for each field's value
- The JS dynamically populates the values from these divs whenever
"Quick Edit" is clicked.

I got my hidden fields into the template with the
quick_edit_custom_box hook, fine. I also did some jQuery to
dynamically add the values needed to each tr.iedit.

But try as I might I couldn't populate them. I had something like this:

$( "form table.page tr.iedit a.editinline" ).click( function() {
[code for populating hidden fields]
return false;
});

But it just wouldn't run. It seemed as if when my function ran, WP's
inlineEditPost function hadn't yet created the Quick Edit box, so the
hidden fields weren't there to populate with values. I tried used
mouseup instead of click, no luck. Is there a clash here? Anyone else
had the same problem?

Steve
_______________________________________________
wp-hackers mailing list
wp-hackers@...
http://lists.automattic.com/mailman/listinfo/wp-hackers

Re: detecting type of edit for parent_save_pre

2009-11-21T10:29:10Z

Just tried this but ran into all sorts of trouble. To be honest I've
lost track of what it was - I think it (or I) got confused about
revisions being saved.

In any case, I've fixed the original problem by detecting
$_POST["attachments"] - it works, at least. I'll put the new, more
serious issue in a new thread.... Bah.

2009/11/20 scribu <scribu@...>:

> You should hook into 'save_post' instead and check by $post->post_type
> instead of relying on the $_POST variable.
>
>
> --
> http://scribu.net
> _______________________________________________
> wp-hackers mailing list
> wp-hackers@...
> http://lists.automattic.com/mailman/listinfo/wp-hackers
>

_______________________________________________
wp-hackers mailing list
wp-hackers@...
http://lists.automattic.com/mailman/listinfo/wp-hackers

Re: Adding Filters

2009-11-20T18:42:50Z

Newbie mistake, I misinterpreted "the_content" in there. - thanks!

-----Original Message-----
From: wp-hackers-bounces@...
[mailto:wp-hackers-bounces@...] On Behalf Of Andrew Nacin
Sent: Friday, November 20, 2009 6:42 PM
To: wp-hackers@...
Subject: Re: [wp-hackers] Adding Filters

>
> add_filter ('get_post_custom_values', 'anti_email_spam', 16);
>

You should read through the Plugin API in the Codex:
http://codex.wordpress.org/Plugin_API.

You don't add a filter to a function; you add it to an API hook that is
built into the WordPress core. the_content() happens to be a function, but
it is also the name of a hook that filters the content returned by that
function, and that's what you're applying the filter to. (
http://adambrown.info/p/wp_hooks/hook/the_content?version=2.8&file=wp-includ
es/post-template.php--
it also is a filter in a few other spots.)
_______________________________________________
wp-hackers mailing list
wp-hackers@...
http://lists.automattic.com/mailman/listinfo/wp-hackers

_______________________________________________
wp-hackers mailing list
wp-hackers@...
http://lists.automattic.com/mailman/listinfo/wp-hackers

Re: Adding Filters

2009-11-20T18:41:46Z

>
> add_filter ('get_post_custom_values', 'anti_email_spam', 16);
>

You should read through the Plugin API in the Codex:
http://codex.wordpress.org/Plugin_API.

You don't add a filter to a function; you add it to an API hook that is
built into the WordPress core. the_content() happens to be a function, but
it is also the name of a hook that filters the content returned by that
function, and that's what you're applying the filter to. (
http://adambrown.info/p/wp_hooks/hook/the_content?version=2.8&file=wp-includes/post-template.php--
it also is a filter in a few other spots.)
_______________________________________________
wp-hackers mailing list
wp-hackers@...
http://lists.automattic.com/mailman/listinfo/wp-hackers