WordPress.org

1. Anonymous
   Unregistered
   Posted 9 years ago #
   

   Hey, great work and congrats on 0.72 beta 1, well done everyone! I've noticed a few bugs, so I thought it would be good to pos them...
   * It says Version 0.71 still in the admin panel (now i'm just being nitpicky!!)
   * XML-RPC with Movable Type API... it doesn't strip_slashes, so when using Zempt - i get a lot of \" and \' etc...
   * Is it just me or is doGeoUrlHeader($posts); meant to make <meta> tags - mine doesn't seem to be doing this. I was using meta tags for GeoURL before - but removed them for this piece of code.
   Good work, anyway... thanks a lot!

2. Matt Mullenweg
   Troublemaker
   Posted 9 years ago #
   

   1. Already fixed.
   2. I'll pass this on to Dougal.
   3. The geoURL functions allow you to attach location information to a specific post and then it does some things with it. Most of the stuff is in index-geo.php, and the header tag being in the normal index.php is a mistake which has been fixed.

3. Anonymous
   Unregistered
   Posted 9 years ago #
   

   * Through XML-RPC, a user who is a lower level can edit someone who has a higher level's entry. I tried this out with a level 3 user editing the level 10 user's post. Surely when you fetch all posts, only posts made by himself and people below him should be allowed.

4. Dougal Campbell
   Member
   Posted 9 years ago #
   

   Totally, I just tested the XML-RPC functions, and both the blogger.editPost and metaWeblog.editPost methods gave me the correct error when I tried to edit a higher level user's post. Can you try your test again, and make doubly sure that you were able to edit a higher level post?

5. Anonymous
   Unregistered
   Posted 9 years ago #
   

   Yes... it did get an error that time - that is weird... but perhaps its me being a fool. Thanks.

6. Anonymous
   Unregistered
   Posted 9 years ago #
   

   * Er... I've just tried editing some posts use w.bloggar - and they disappeared! Looking through the database with phpMyAdmin, I've seen the date/time has been set to 0000-00-00 00:00:00...

7. Anonymous
   Unregistered
   Posted 9 years ago #
   

   Hello? Has anything been done about this?

8. Anonymous
   Unregistered
   Posted 9 years ago #
   

   in my case posting with w.bloggar set posts date to 01-01-1970

9. Anonymous
   Unregistered
   Posted 9 years ago #
   

   Well, yes, thats the Unix Epoch. I realised mine is set to that too... Dougal? Anything?

10. Anonymous
    Unregistered
    Posted 9 years ago #
    

    i get this error too? anythign to be done about it?

11. Dougal Campbell
    Member
    Posted 9 years ago #
    

    Will look into it ASAP. Are you seeing it with new posts, or just edited posts?

12. Dougal Campbell
    Member
    Posted 9 years ago #
    

    Okay, found the bug, squished it, and gave it a burial at sea. Fix commited to CVS.

13. Anonymous
    Unregistered
    Posted 9 years ago #
    

    Thanks mate... been waiting a while for a response - sorry if I seemed a little harsh. Thanks again!

14. codergurl
    Member
    Posted 9 years ago #
    

    hey, where's the upload button in the admin panel? I know its wp-admin/b2uploads.php, but still...

15. Mike Little
    Member
    Posted 9 years ago #
    

    Check your settings under options -> file uploads. I think it is off by default.
    Mike

16. lars
    Member
    Posted 9 years ago #
    

    Not sure if this is a bug, but entering the following lines in the Post/Edit textarea (note the blank lines inbetween):
    paragraph
    <h4>Heading</h4>
    paragraph
    results in the following output (note the extra paragraph inserted):
    paragraph
    <h4>Heading</h4>
    paragraph
    while the same input *without* blank lines:
    paragraph
    <h4>heading</h4>
    paragraph
    outputs the following (note the inserted
    ):
    paragraph
    <h4>heading</h4>
    paragraph
    A similar thing happens with this input:

    bla bla bla

    which outputs as:

    bla bla bla

    Again, an additional paragraph gets inserted.
    /Lars (on WordPress 0.72b)

17. lars
    Member
    Posted 9 years ago #
    

    Problem solved!
    In b2vars.php, I removed/commented the following line (near the end):
    add_filter('the_content', 'wpautop');
    I'm surprised no one else has noticed that this results in nonvalid markup. Could it be just my installation?
    If not, and unless this filter does something really useful that I haven't noticed, may I suggest to turn it off by default?
    /Lars

18. Matt Mullenweg
    Troublemaker
    Posted 9 years ago #
    

    Actually I think the problem is you are using an old version. autop is very useful because it converts new lines into paragraphs and breaks. Most systems just put a
    at the end of everything but autop intelligently creates paragraphs with regard to other block level tags. So in all your examples you would never need to type or because it is taken care of automatically. The behaviour you describe is consistent with an older version, I tested your examples with the latest code and had no problems.

19. southerngal
    Member
    Posted 9 years ago #
    

    How about the bug I posted, allusion? It's kind of frustrating to a degree of not being able to quick post a comment while I'm still in the post/edit screen. Of course it's not life or death either! ;)

20. lars
    Member
    Posted 9 years ago #
    

    autop:
    I'm on 0.72 beta, but probably not the latest build. I'll try and upgrade, and then test again. Do I need to update all files?
    As for autop, I'm sure a lot of users will find it extremely useful.
    However, because I like to handcode my html, I still prefer having a manual option. It gives me a sense of control.
    A suggestion would be include this as an admin interface option, with an explanation of what autop does.
    /Lars

21. southerngal
    Member
    Posted 9 years ago #
    

    Thanks Mike! :) I will wait till the final release is made, soon right? ;)

Topic Closed

This topic has been closed to new replies.