[wp-hackers] RE: wp-hackers Digest, Vol 48, Issue 48
donny schuurman
donny_loverboy at live.nl
Sat Jan 17 08:09:43 GMT 2009
fuck off
> From: wp-hackers-request at lists.automattic.com
> Subject: wp-hackers Digest, Vol 48, Issue 48
> To: wp-hackers at lists.automattic.com
> Date: Fri, 16 Jan 2009 18:45:00 +0000
>
> Send wp-hackers mailing list submissions to
> wp-hackers at lists.automattic.com
>
> To subscribe or unsubscribe via the World Wide Web, visit
> http://lists.automattic.com/mailman/listinfo/wp-hackers
> or, via email, send a message with subject or body 'help' to
> wp-hackers-request at lists.automattic.com
>
> You can reach the person managing the list at
> wp-hackers-owner at lists.automattic.com
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of wp-hackers digest..."
>
>
> Today's Topics:
>
> 1. Re: Plugin Upgrade Failing when using Subversion (Mike Schinkel)
> 2. Re: Set a unique directory for uploads (Chris Jean)
> 3. Re: Plugin Upgrade Failing when using Subversion
> (Harish Narayanan)
> 4. Re: Set a unique directory for uploads (Jos? Fontainhas)
> 5. Re: Ignore Portions of URI (scribu)
> 6. Comments popup (scribu)
> 7. Re: Ignore Portions of URI (Mike Schinkel)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Fri, 16 Jan 2009 10:12:33 -0600 (CST)
> From: Mike Schinkel <mikeschinkel at newclarity.net>
> Subject: Re: [wp-hackers] Plugin Upgrade Failing when using Subversion
> To: wp-hackers at lists.automattic.com
> Message-ID: <22234214.871232122352266.JavaMail.DELL-1405$@Dell-1405>
> Content-Type: text/plain; charset=utf-8
>
> > Basically, I'm asking why do you want to use SVN to keep the core up
> to date, but the plugin upgrader to keep the plugins up-to-date?
> You're mixing two different ways of doing the same thing here. Choose
> one, then use that one for both cases. All the plugins in Extend are
> available via SVN too.
>
> Thanks for clarifying.
>
> Read my most recent earlier email on that subject, but in a nutshell our use-case is different. I deliver the code to my client (the interactive agency) via SVN; it is their SVN server. I use SVN to archive software that can be completely rebuilt from scratch by them, including SQL scripts to initialize plugins to the proper state, so they need zero knowledge of where to find WordPress things and have no dependency on trying to find those things when they need to rebuild a system for testing and then for deployment.
>
> Tell me if you think otherwise but I think my use-cases make more sense when working on a large team with lots of players many of who don't know anything more about WordPress than it's name, and yours make more sense when working on a small team of WordPress gurus?
>
> -Mike Schinkel
> http://mikeschinkel.com/
>
>
> ------------------------------
>
> Message: 2
> Date: Fri, 16 Jan 2009 10:16:12 -0600
> From: Chris Jean <gaarai at gaarai.com>
> Subject: Re: [wp-hackers] Set a unique directory for uploads
> To: wp-hackers at lists.automattic.com
> Message-ID: <4970B2CC.80406 at gaarai.com>
> Content-Type: text/plain; charset=ISO-8859-1; format=flowed
>
> I guess it depends on where you put the code and how your site is set
> up. I did this on a stock install of 2.7 with no plugins and put the
> code at the end of the functions.php file of the default theme.
>
> No warnings or errors were generated by this change and all the pages
> functioned properly. Well, all the pages I tested worked correctly. I
> checked again, and my Tools page worked just fine.
>
> It's possible that a plugin or theme feature is causing this failure, so
> I wouldn't know exactly what the problem is nor how to fix it unless I
> were to get more details about what you are running on the site or
> access to the site itself.
>
> You might try disabling all your plugins first and seeing if the problem
> goes away. If the problem goes away, then activate plugins one at a time
> until the problem comes back. That will tell you if a plugin is causing
> the problem and specifically which one it is.
>
> Chris Jean
> http://gaarai.com/
> http://wp-roadmap.com/
>
>
>
> Mário Gamito wrote:
> > Hi Gaarai,
> >
> > Thank you for your answer.
> >
> > Gaarai wrote:
> >
> >> add_filter( 'intermediate_image_sizes',
> >> 'remove_intermediate_image_sizes' );
> >> function remove_intermediate_image_sizes( $sizes ) {
> >> return array();
> >> }
> >>
> >> This could simply be added to your functions.php file in the theme. I
> >> tested it this way, and it worked perfectly.
> >>
> > Yes, it works. Although I get the "headres already sent" warning after
> > the crunching.
> >
> > But the worst part is that it breaks the tools page. I get a blank page.
> >
> > Any ideias ?
> >
> > Warm Regards,
> >
>
>
> ------------------------------
>
> Message: 3
> Date: Fri, 16 Jan 2009 17:26:36 +0100
> From: Harish Narayanan <harish.mlists at gmail.com>
> Subject: Re: [wp-hackers] Plugin Upgrade Failing when using Subversion
> To: wp-hackers at lists.automattic.com
> Message-ID: <4970B53C.3010305 at gmail.com>
> Content-Type: text/plain; charset=UTF-8
>
> Mike Schinkel wrote:
> >> I set these properties by connecting to my server
> >> via ssh, navigating to the appropriate folders and
> >> using svn propset. Look for svn:ignore on the
> >> following page for detailed information:
> >> http://svnbook.red-bean.com/en/1.1/ch07s02.html
> >
> > Thanks, I'll check it out, but probably after this project though; don't have time to become an SVN expert before launch, unfortunately. :-(
>
> All right.
>
> >> See if this makes sense, as I am doing something
> >> fundamentally different:
> >
> > Yes, it does make sense. What's different is I'm developing locally for a (near-)future deployment. I think the difference is we are not making any changes on a live server until they first go from dev to staging/testing, then to live. SVN used on dev but not on stage/test or live.
>
> I understand, but the persnickety step is really the same. Since my
> journal is not mission critical (hah!), what you call staging/testing is
> my live implementation.
>
> >> To avoid any confusion, I keep anything that's
> >> not part of the default WordPress repository
> >> explicitly out of this revision control---
> >> which is what I was advising you to do.
> >
> > Given our use case, which is partially to archive and partially to be able to recreate a fully working implementation, that doesn't really work for us, unfortunately. Wish it did.
>
> I only said keep things external to WordPress out of the original
> repository. You can easily have a separate repository for your plug-in
> additions/changes or your theme development. But that's a story for
> another day. I wish you luck on finding something that works in the
> short term for your current project.
>
> > Thanks for the help.
>
> Glad to help.
>
> Harish
>
>
> ------------------------------
>
> Message: 4
> Date: Fri, 16 Jan 2009 16:35:48 +0000
> From: Jos? Fontainhas <jfontainhas at gmail.com>
> Subject: Re: [wp-hackers] Set a unique directory for uploads
> To: wp-hackers at lists.automattic.com
> Message-ID: <4970B764.4010908 at gmail.com>
> Content-Type: text/plain; charset=ISO-8859-1; format=flowed
>
>
> Tried it just now, and works like a charm (and comes in quite handy,
> too. Thanks Gaarai). Which php file is complaining that the headers have
> already been sent, exactly?
>
> -Zé
>
> > Mário Gamito wrote:
> >> Hi Gaarai,
> >>
> >> Thank you for your answer.
> >>
> >> Gaarai wrote:
> >>
> >>> add_filter( 'intermediate_image_sizes',
> >>> 'remove_intermediate_image_sizes' );
> >>> function remove_intermediate_image_sizes( $sizes ) {
> >>> return array();
> >>> }
> >>>
> >>> This could simply be added to your functions.php file in the theme. I
> >>> tested it this way, and it worked perfectly.
> >>>
> >> Yes, it works. Although I get the "headres already sent" warning after
> >> the crunching.
> >>
> >> But the worst part is that it breaks the tools page. I get a blank page.
> >>
> >> Any ideias ?
> >>
> >> Warm Regards,
> >>
> > _______________________________________________
> > wp-hackers mailing list
> > wp-hackers at lists.automattic.com
> > http://lists.automattic.com/mailman/listinfo/wp-hackers
> >
>
>
>
> ------------------------------
>
> Message: 5
> Date: Fri, 16 Jan 2009 19:56:38 +0200
> From: scribu <scribu at gmail.com>
> Subject: Re: [wp-hackers] Ignore Portions of URI
> To: wp-hackers at lists.automattic.com
> Message-ID:
> <349fe48b0901160956n6a698b59xa169b2045fa2c3bd at mail.gmail.com>
> Content-Type: text/plain; charset=UTF-8
>
> On Fri, Jan 16, 2009 at 4:25 PM, Dougal Campbell <dougal at gunters.org> wrote:
>
> > Otto wrote:
> >
> >> You can do a search, then rearrange or hide various news sources. Your
> >>> view
> >>> state is stored in the hash portion of the URL, which makes it
> >>> bookmarkable,
> >>> without cookies. So you can send the bookmark to other users, and they
> >>> get
> >>> the same search view that you set up. For example:
> >>>
> >>> http://addictomatic.com/topic/wordpress#kmun.dwqo.tblh
> >>>
> >>>
> >>
> >> How is that a substantial improvement over, say,
> >> http://addictomatic.com/topic/wordpress?status=kmun.dwqo.tblh ?
> >>
> >> I just don't see how getting hash info from the URL and sending it via
> >> JS is any better than a GET URL.
> >>
> >>
> >
> > For one thing, it looks cleaner. For another, you don't have to be
> > concerned about whether or not search engines are indexing querystrings. So
> > you get cleaner analytics, and hopefully better SEO.
> >
> > And all the cool kids are doing it.
>
>
> Not to mention that you might avoid several full page reloads.
>
> --
> http://scribu.net
>
>
> ------------------------------
>
> Message: 6
> Date: Fri, 16 Jan 2009 20:17:44 +0200
> From: scribu <scribu at gmail.com>
> Subject: [wp-hackers] Comments popup
> To: wp-hackers at lists.automattic.com
> Message-ID:
> <349fe48b0901161017h14766890xbaf97168d1e9ead6 at mail.gmail.com>
> Content-Type: text/plain; charset=UTF-8
>
> Is there still any valid reason for disabling
> comment_popup_link()<http://trac.wordpress.org/browser/tags/2.7/wp-includes/comment-template.php#L882>on
> single posts?
>
> I commented out the two lines (905, 906) and it works just fine on single
> posts.
>
> --
> http://scribu.net
>
>
> ------------------------------
>
> Message: 7
> Date: Fri, 16 Jan 2009 12:43:25 -0600 (CST)
> From: Mike Schinkel <mikeschinkel at newclarity.net>
> Subject: Re: [wp-hackers] Ignore Portions of URI
> To: wp-hackers at lists.automattic.com
> Message-ID: <9005852.981232131408937.JavaMail.DELL-1405$@Dell-1405>
> Content-Type: text/plain; charset=utf-8
>
> Hi All:
>
> Hate to get mired into this debate, but finally I can't help myself but make the following points (and I've spent a lot of time researching URL design, see: http://blog.welldesignedurls.org.)
>
> URL fragments and URL parameters create different architectures and really should be used for different use-cases.
>
> When using URL Fragments you are essentially creating a mini-app within one URL where the fragment is ideally being used to capture and restore state when a user bookmarks the URL. URL fragments are handled completely by the client although some (all?) search engines will index fragments with their URLs.
>
> URL Parameters are used when you want the server to generate a completely different response representation upon a request. BTW, URLs with parameters (i.e. http://example.com/?p=3) and URLs with parameter data embedded (i.e. http://example.com/about/) are equivalent for the purpose of this discussion.
>
> For example the project that I am working on today will use both parameters and fragments for a media gallery with video and photo tabs. URLs will look like this:
>
> http://example.com/gallery/videos
> http://example.com/gallery/photos
>
> The Video Gallery will have "Channels" and "Videos" where a Channel contains one of more videos. The Photo Gallery will have "Albums" and "Photo Sets" where an Album contains one of more Photo Sets which contains one of more Photos. We want the screen to refresh *between* the video and photo section since we are using different players and all the data on the screen chances but we want full interactivity and quick response *within* the video and the photo galleries *and* we want to be able to bookmark the current state. These are some example URLs w/fragments we'll use:
>
> http://example.com/gallery/videos#vc3v52
> http://example.com/gallery/photos#pa2ps7p86
>
> In those fragments vc=Video Channel, v=Video, pa=Photo Album, ps=Photo Set, and p=Photo with the numbers being their respective IDs from the NextGen Gallery (I'm planning to enhance NextGen to support video.)
>
> As the user clicks around in the video and/or photo gallery we'll use Javascript to update the URL to indicate the current "state" of the page/mini-app. When a user returns to a bookmarked URL with those fragments we'll use Javascript to restore the page state to the Channel/Video and/or the Album/PhotoSet/Photo that was being displayed when the URL was bookmarked.
>
> That said, you can potentially use page refreshes (URLs w/parameters) for everything or use in-page navigation (URLs w/fragments) for everything but each creates a different architecture and thus should be used in the use cases that best fit the architecture. For example two completely different pages shouldn't use URL fragments to differentiate but a page with a single cohesive purpose that requires lots of interactivity (like, say, a file manager for server files) should use URL fragments and it should regenerate the relevant state the page was in when bookmarked from the URL fragment. BTW, this is one thing that most Flash apps do NOT do well, unfortunately.
>
> So in summary, URLs w/parameters and URLs w/fragments are both valid architectures but each should be used with their respective appropriate use-cases.
>
> HTH.
>
> -Mike Schinkel
> http://mikeschinkel.com/
>
> P.S. The HTTP spec says that it is up to the client to interpret the URL fragment and that mostly it should do so based on content type. For example, think of how fragments work with PDF files. In the case of HTML the browser does have default behavior for fragment, i.e. repositioning the viewport, but for HTML+AJAX/AHAH-based apps repositioning only is too limited. In essence, when we use fragments we should design them as if we were designing our own new custom content type that is based on HTML+interactivity.
>
>
> ------------------------------
>
> _______________________________________________
> wp-hackers mailing list
> wp-hackers at lists.automattic.com
> http://lists.automattic.com/mailman/listinfo/wp-hackers
>
>
> End of wp-hackers Digest, Vol 48, Issue 48
> ******************************************
_________________________________________________________________
Nieuw: nu ook chatten op je mobiel!
http://www.overaljevriendenbijje.nl/#superdeal
More information about the wp-hackers
mailing list