[wp-hackers] Moving from dev to live, and relative vs absolute
mickey panayiotakis
mickey at infamia.com
Sat Oct 29 21:45:01 UTC 2011
I db-wrangle but I'm curious,: if the issue is content links, does anyone
use wordpress' content export/import feature?
On Oct 29, 2011 4:35 PM, <wp-hackers-request at lists.automattic.com> wrote:
> 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. Truce? (Brian Fegter)
> 2. Re: Two new, long-overdue plugins to make your wordpress life
> a little easier... (sam auciello)
> 3. Re: Two new, long-overdue plugins to make your wordpress life
> a little easier... (Mike Little)
> 4. Re: Two new, long-overdue plugins to make your wordpress life
> a little easier... (Mike Little)
> 5. Re: Occupy Wall Street: WordPress hackers wanted (Dan Phiffer)
> 6. What to do when Blogger don?t let you go? (Diana K. Cury)
> 7. Re: Two new, long-overdue plugins to make your wordpress life
> a little easier... (Rafael Ehlers)
> 8. Re: Two new, long-overdue plugins to make your wordpress life
> a little easier... (Marcus Pope)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Sat, 29 Oct 2011 09:04:16 -0400
> From: Brian Fegter <brian at fegter.com>
> Subject: [wp-hackers] Truce?
> To: wp-hackers at lists.automattic.com
> Message-ID:
> <CAPtWN+ysw=qyAD2G4Q_UUFLOkhCQ0S2h2XF9obR+FeKc3SCtww at mail.gmail.com
> >
> Content-Type: text/plain; charset=ISO-8859-1
>
> http://b1ff.me/sNq0aV
>
>
> ------------------------------
>
> Message: 2
> Date: Sat, 29 Oct 2011 10:51:36 -0400
> From: sam auciello <info at samauciello.com>
> Subject: Re: [wp-hackers] Two new, long-overdue plugins to make your
> wordpress life a little easier...
> To: wp-hackers at lists.automattic.com
> Message-ID:
> <CAGXuZ6vR7F7p57sMU5e6KFf7t33K_RKieHh8Qh5JRdDLMja+mQ at mail.gmail.com
> >
> Content-Type: text/plain; charset=ISO-8859-1
>
> If I may put in my two cents to the absolute vs relative uri debate. I am
> a relative newb to the web dev world and most of my work with WP is for
> single sites for small businesses that may or may not want a blog.
> Basically we use WP as a CMS becuase it's light-weight and easy to use.
> For this reason, I've only recently started using version control systems.
> My typical workflow is
>
> 1. Client hires me to upgrade their site to WP
> 2. I create a WP installation at example.com/wp and set up the necessary
> themes/plugins etc.
> 3. The create content.
> 4. Once we're satisfied we go live. The process for this is here:
> http://codex.wordpress.org/Moving_WordPress
>
> I am almost always frustrated by the fact that this is a 16 step process
> but more importantly I often forget step 11, and my client is confused as
> to why all of their images won't show up. I realize that I'm probably not
> doing it right and would love suggestions on this, but the point is that my
> approach isn't fundamentally stupid for my use case. I'm guessing lots of
> people have run into this exact issue. Relative URLs would fix this. I
> don't know enough about the various security concerns etc. to say more but
> I would certainly love to see a constant, something like WP_RELATIVE_PATHS,
> that I could set to true at the beginning that would turn on the correct
> export filters and change the way things were put into the content in the
> first place.
>
> Peace
> ~Sam
>
>
> ------------------------------
>
> Message: 3
> Date: Sat, 29 Oct 2011 16:09:52 +0100
> From: Mike Little <wordpress at zed1.com>
> Subject: Re: [wp-hackers] Two new, long-overdue plugins to make your
> wordpress life a little easier...
> To: wp-hackers at lists.automattic.com
> Message-ID:
> <CAMb54M0LpgoObubCkN9=v7ZcZc3qJyaZ_aSC1NW7d6yGCb7HPQ at mail.gmail.com
> >
> Content-Type: text/plain; charset=UTF-8
>
> On Sat, Oct 29, 2011 at 02:59, Marcus Pope <Marcus.Pope at springbox.com
> >wrote:
>
> > Mike Little, I know I said I'd drop the topic on this list, but I didn't
> > want to ignore your requests for information.
> >
> > You can look at the patch I referenced, you'll see line numbers and file
> > names, there are a lot of references so it's just easier to look here...
> > http://core.trac.wordpress.org/attachment/ticket/19037/ssl.patch
> >
> > Everything that passes through things like get_site_url in
> > link-template.php, self_link in feed.php, class-wp-xmlrpc-server.php etc
> > gets processed, and there are a bunch of links that go through those low
> > level functions.
> >
> >
> But there are not *content* urls. These are the app urls to take you to the
> edit page or the plugins page . They *have* to change from one site to
> another, and because WordPress allows you to run the back end half of your
> installation on https separate from the front end half, then yes, there
> *has* to be a check and a possible replace http for htps. But, as I say,
> this is the back end admin functions and those are accessed very
> infrequently compared to the front end *content*
>
> This example does not support your case.
>
>
> Mike
> --
> Mike Little
> http://zed1.com/
>
>
> ------------------------------
>
> Message: 4
> Date: Sat, 29 Oct 2011 16:23:27 +0100
> From: Mike Little <wordpress at zed1.com>
> Subject: Re: [wp-hackers] Two new, long-overdue plugins to make your
> wordpress life a little easier...
> To: wp-hackers at lists.automattic.com
> Message-ID:
> <CAMb54M0TpBD-TucGOh92Rtxb6jtS4Bx75YNETtpxnBNaHphRXA at mail.gmail.com
> >
> Content-Type: text/plain; charset=UTF-8
>
> On Sat, Oct 29, 2011 at 15:51, sam auciello <info at samauciello.com> wrote:
>
> > If I may put in my two cents to the absolute vs relative uri debate. I
> am
> > a relative newb to the web dev world and most of my work with WP is for
> > single sites for small businesses that may or may not want a blog.
> > Basically we use WP as a CMS becuase it's light-weight and easy to use.
> > For this reason, I've only recently started using version control
> systems.
> > My typical workflow is
> >
> > 1. Client hires me to upgrade their site to WP
> > 2. I create a WP installation at example.com/wp and set up the necessary
> > themes/plugins etc.
> >
>
> Here's the bit where you are going wrong! By doing this you are *creating*
> the pain. And relative URLs would not stop this.
>
> See my tips (below) (and in one of these threads) for making it easy to
> transfer from development site to live site
>
>
>
>
> > 3. The create content.
> > 4. Once we're satisfied we go live. The process for this is here:
> > http://codex.wordpress.org/Moving_WordPress
> >
> > I am almost always frustrated by the fact that this is a 16 step process
> > but more importantly I often forget step 11, and my client is confused as
> > to why all of their images won't show up. I realize that I'm probably
> not
>
> doing it right and would love suggestions on this,
>
>
> As I mentioned elsewhere, get your self a short domain. Create your clients
> site on a subdomain of it (with a character count exactly the same length
> of
> the live domain) so that wordPress is in the root of the site. Install
> plugins, themes, tweak and deveop, add content.
> When ready to go live:
> DB dump,
> search and replace developdomain with livedomain,
> db load on live.
> transfer all files from dev to live.
> Done. 4 steps.
>
> It usually takes me a few minutes, always less than 30 minutes (depending
> on
> the amount of files and content) and *never* goes wrong.
>
>
>
>
>
>
> > but the point is that my
> > approach isn't fundamentally stupid for my use case. I'm guessing lots
> of
> > people have run into this exact issue. Relative URLs would fix this.
>
>
>
> No they wouldn't: /wp/wp-content/uploads/2011/10/29/my-images.jpg still
> needs to be changed to /wp-content/uploads/2011/10/29/my-images.jpg
> regardless of whether it start with the domain or not.
>
>
>
> Mike
> --
> Mike Little
> http://zed1.com/
>
>
> ------------------------------
>
> Message: 5
> Date: Sat, 29 Oct 2011 11:27:13 -0400
> From: Dan Phiffer <dan at phiffer.org>
> Subject: Re: [wp-hackers] Occupy Wall Street: WordPress hackers wanted
> To: wp-hackers at lists.automattic.com
> Message-ID: <DCF068E6-B8A0-46A2-8AA0-D19DD31E849D at phiffer.org>
> Content-Type: text/plain; charset=us-ascii
>
> Here is the URL in case anyone is interested in this:
>
> http://jobs.wordpress.net/2011/10/26/occupy-wall-street-nyc-general-assembly/
>
> (Sorry!)
>
> On Oct 26, 2011, at 12:50 PM, Dan Phiffer wrote:
>
> > Sorry about that!
> >
> > POST*D
> >
> >
> > On Oct 26, 2011, at 8:53 AM, Brian Fegter wrote:
> >
> >> Dan,
> >>
> >> This is not Occupy WP Hackers with job postings. Feel free to occupy
> >> http://jobs.wordpress.net/
> >>
> >> BF
> >> _______________________________________________
> >> wp-hackers mailing list
> >> wp-hackers at lists.automattic.com
> >> http://lists.automattic.com/mailman/listinfo/wp-hackers
> >
> > _______________________________________________
> > wp-hackers mailing list
> > wp-hackers at lists.automattic.com
> > http://lists.automattic.com/mailman/listinfo/wp-hackers
>
>
>
> ------------------------------
>
> Message: 6
> Date: Sat, 29 Oct 2011 15:07:39 -0300
> From: "Diana K. Cury" <dianakac at gmail.com>
> Subject: [wp-hackers] What to do when Blogger don?t let you go?
> To: <wp-hackers at lists.automattic.com>
> Message-ID: <00a601cc9665$a8c7ee40$0100a8c0 at corpfe1f3cd943>
> Content-Type: text/plain; charset="iso-8859-1"
>
> Once and a while I'm questioned about Blogger limiting posts when
> exporting/migrating. Is that a local issue, an user misuse or really a
> Blogger limitation?!
>
> WordPress.com to WordPress hosted is quite simples and neat, but Blogger
> makes life harder. I heard that Blogger users must try to import between
> Blogger and WordPress.com, so servers will connect at least, then export to
> hosted WordPress, is that a fact?! Never had a huge Blogger myself, so I
> really know nothing about all this.
>
> Thanks for any advice
>
> ------------------------------
>
> Message: 7
> Date: Sat, 29 Oct 2011 16:48:24 -0300
> From: Rafael Ehlers <rafaehlers at gmail.com>
> Subject: Re: [wp-hackers] Two new, long-overdue plugins to make your
> wordpress life a little easier...
> To: wp-hackers at lists.automattic.com
> Message-ID:
> <CAF_6N0PBeidjcA30affwMOJD_o+Y23GbZu_LzrseoSBTLPiuhQ at mail.gmail.com
> >
> Content-Type: text/plain; charset=ISO-8859-1
>
> Mike Little wrote: "(with a character count exactly the same length of
> the live domain)"
>
> Aw c'mon, no offense to Mike, but that's just ridiculous, please,
> seriously, just use this script:
>
>
> http://www.interconnectit.com/wp-content/uploads/2011/05/searchreplacedb2.zip
>
> It's an easy process:
>
> 1. Change DB Connection in wp-config.php
> 2. Upload all WP files from local to production (and searchreplacedb.php to
> root file of wp)
> 3. Export DB from local to production
> 4. Run searchreplacedb.php
> 5. Log in to WordPress -> Settings -> Save Permalinks (to regenerate)
> 6. Profit!!!
>
>
> Seriously, use that script!
>
> Best regards,
>
> Rafael Ehlers
>
> On Sat, Oct 29, 2011 at 12:23 PM, Mike Little <wordpress at zed1.com> wrote:
>
> > On Sat, Oct 29, 2011 at 15:51, sam auciello <info at samauciello.com>
> wrote:
> >
> > > If I may put in my two cents to the absolute vs relative uri debate. I
> > am
> > > a relative newb to the web dev world and most of my work with WP is for
> > > single sites for small businesses that may or may not want a blog.
> > > Basically we use WP as a CMS becuase it's light-weight and easy to use.
> > > For this reason, I've only recently started using version control
> > systems.
> > > My typical workflow is
> > >
> > > 1. Client hires me to upgrade their site to WP
> > > 2. I create a WP installation at example.com/wp and set up the
> necessary
> > > themes/plugins etc.
> > >
> >
> > Here's the bit where you are going wrong! By doing this you are
> *creating*
> > the pain. And relative URLs would not stop this.
> >
> > See my tips (below) (and in one of these threads) for making it easy to
> > transfer from development site to live site
> >
> >
> >
> >
> > > 3. The create content.
> > > 4. Once we're satisfied we go live. The process for this is here:
> > > http://codex.wordpress.org/Moving_WordPress
> > >
> > > I am almost always frustrated by the fact that this is a 16 step
> process
> > > but more importantly I often forget step 11, and my client is confused
> as
> > > to why all of their images won't show up. I realize that I'm probably
> > not
> >
> > doing it right and would love suggestions on this,
> >
> >
> > As I mentioned elsewhere, get your self a short domain. Create your
> clients
> > site on a subdomain of it (with a character count exactly the same length
> > of
> > the live domain) so that wordPress is in the root of the site. Install
> > plugins, themes, tweak and deveop, add content.
> > When ready to go live:
> > DB dump,
> > search and replace developdomain with livedomain,
> > db load on live.
> > transfer all files from dev to live.
> > Done. 4 steps.
> >
> > It usually takes me a few minutes, always less than 30 minutes (depending
> > on
> > the amount of files and content) and *never* goes wrong.
> >
> >
> >
> >
> >
> >
> > > but the point is that my
> > > approach isn't fundamentally stupid for my use case. I'm guessing lots
> > of
> > > people have run into this exact issue. Relative URLs would fix this.
> >
> >
> >
> > No they wouldn't: /wp/wp-content/uploads/2011/10/29/my-images.jpg still
> > needs to be changed to /wp-content/uploads/2011/10/29/my-images.jpg
> > regardless of whether it start with the domain or not.
> >
> >
> >
> > Mike
> > --
> > Mike Little
> > http://zed1.com/
> > _______________________________________________
> > wp-hackers mailing list
> > wp-hackers at lists.automattic.com
> > http://lists.automattic.com/mailman/listinfo/wp-hackers
> >
>
>
> ------------------------------
>
> Message: 8
> Date: Sat, 29 Oct 2011 16:33:10 -0400
> From: Marcus Pope <Marcus.Pope at springbox.com>
> Subject: Re: [wp-hackers] Two new, long-overdue plugins to make your
> wordpress life a little easier...
> To: "wp-hackers at lists.automattic.com"
> <wp-hackers at lists.automattic.com>
> Message-ID: <6B80B0F0-D0A7-4857-AA21-9147F5DAE9AE at springbox.com>
> Content-Type: text/plain; charset="us-ascii"
>
> Mike, app urls do not have to change or be post processed. With
> root-relative urls you inherently do not specify http or https on links
> returned to the browser and the browser will maintain that ssl connection
> for you, guaranteed. In the event that someone navigates directly to an
> http url when they should have gone to https wordpress already does a
> redirect to the proper scheme.
>
> They do not apply to back end functions only. Install my plugin and browse
> a front end page. You will see just how often they are called with a simple
> debug statement to your error log. get_site_url and others in that patch
> are universally executed functions (front and back.)
>
> Hope that information helps you find what I'm referring to.
>
> Marcus Pope
> Senior Developer
> Springbox
> 512-968-3585
>
> On Oct 29, 2011, at 10:10 AM, "Mike Little" <wordpress at zed1.com> wrote:
>
> > On Sat, Oct 29, 2011 at 02:59, Marcus Pope <Marcus.Pope at springbox.com
> >wrote:
> >
> >> Mike Little, I know I said I'd drop the topic on this list, but I didn't
> >> want to ignore your requests for information.
> >>
> >> You can look at the patch I referenced, you'll see line numbers and file
> >> names, there are a lot of references so it's just easier to look here...
> >> http://core.trac.wordpress.org/attachment/ticket/19037/ssl.patch
> >>
> >> Everything that passes through things like get_site_url in
> >> link-template.php, self_link in feed.php, class-wp-xmlrpc-server.php etc
> >> gets processed, and there are a bunch of links that go through those low
> >> level functions.
> >>
> >>
> > But there are not *content* urls. These are the app urls to take you to
> the
> > edit page or the plugins page . They *have* to change from one site to
> > another, and because WordPress allows you to run the back end half of
> your
> > installation on https separate from the front end half, then yes, there
> > *has* to be a check and a possible replace http for htps. But, as I say,
> > this is the back end admin functions and those are accessed very
> > infrequently compared to the front end *content*
> >
> > This example does not support your case.
> >
> >
> > Mike
> > --
> > Mike Little
> > http://zed1.com/
> > _______________________________________________
> > wp-hackers mailing list
> > wp-hackers at lists.automattic.com
> > http://lists.automattic.com/mailman/listinfo/wp-hackers
>
>
> ------------------------------
>
> _______________________________________________
> wp-hackers mailing list
> wp-hackers at lists.automattic.com
> http://lists.automattic.com/mailman/listinfo/wp-hackers
>
>
> End of wp-hackers Digest, Vol 81, Issue 62
> ******************************************
>
More information about the wp-hackers
mailing list