58

A long time ago I came across a graphic which presented it like this: Code should flow in this direction: Development >> Staging >> Production Content, on the other hand, should flow in the opposite direction: Development << Staging << Production That is, you should populate your development and staging environments with live content (to ...


25

In short, we handle these issues on a case-by-case basis. Adrian described it well. Here are two slides from a presentation I did on the topic: schema flow & content flow The thing that makes the described process easy for us is that we rarely work on multiple large features at a time. We build one, deploy. Build another, deploy. So we don't have to ...


9

I outlined some of the methodologies I have encountered for handling migrations in my EECI talk where I demoed Site Manager. You can find my slide deck here: https://speakerdeck.com/chrisimrie/eeci-2012-us-ee-and-web-agency Thanks for the kind words about Site Manager. Early days, but it is definitely our solution to migrating content between local/dev/...


7

I haven't tested this either, but I'm not sure @adrienne's htaccess will work. I'd do it like this: RewriteEngine on # 301 redirect path.html to just path RewriteCond %{REQUEST_FILENAME} !-d RewriteCond %{REQUEST_FILENAME} !-f RewriteRule ^(.*)\.html$ $1 [R=301,L] # the rest of your rewrite rules (e.g. removing index.php) go here RewriteCond $1 !\.(gif|...


6

You don't need to redirect them individually in .htaccess; you can do a rewrite to strip .html, as you were told. Below is a set of directives that should both route whatever.html to /index.php/whatever/ (for EE) and then remove index.php from everything else. This is, however, not tested, so it might require refinement. RewriteEngine on RewriteCond %{...


4

If you're just looking for a convenient way to transfer the latest data from one database to another (say from the production database into your development database) then Navicat's data transfer feature is very handy. Though it accomplishes the same thing as the manual export/import you referred to, and will overwrite data not sync it, it's a lot more ...


4

Pixel and Tonic updated Assets to account for $config overrides. Update to 2.0.2 and you should be set! http://pixelandtonic.com/assets/releasenotes


3

Few things I'd try first: Have you tried adding the ? to the approved method after index.php? If that doesn't work, have you tried adding ? before /news/post/$4 to see if that changes anything? Check your $config['uri_protocol'] or add it to your config and change from AUTO to one of the other settings (check http://devot-ee.com/ee-config-vars to see the ...


3

I follow pretty much just what Adrian Macneil explained. I use git and Beanstalk for deployments. It makes it easy to deploy one branch (dev for example) to the staging server online. Once that code is all ready, I merge it with the production branch, and deploy that to the live/production server. For future reference, there's an add-on being developed for ...


3

All credit goes to Brandon. I searched and found this thread last night which was ultimately the solution. I'll post the script below as that thread was a little confusing to follow until they got it working. You'll need to convert all MH File fields to a Matrix field first. Then run the script below. Make sure to replace XX with your Matrix field ID, YY ...


2

I would recommend looking at the database migration features of HeidiSQL and Navicat. They both provide robust migration mechanisms that can synchronize the MySQL database underlying your EE instances.


2

Just published an addon on github to trace db changes into files that can be deployed to your staging server. On the staging server you can re-execute the db changes made on your local development environment (manual or use a hook). The basics work, but lots of room for improvement. https://github.com/fccotech/ee-db-trace Feel free to use/extend/branch ...


2

We not merged like this, but I would probably go about it like this: set up the main site set up the msm sites and don't import any channels. upgrade all EE1 sites (you can check license, but I'm pretty sure if you do this locally, you aren't breaking any rules) use field editor from mighty big root to export the channel fields and import them into the new ...


2

I think your rule is being evaluated at least twice and returns a match twice, once before and once after you do your index.php hiding. You must be more narrow about what you are matching on. I think this will do the trick: RedirectMatch 301 ^index.php/news/([0-9]+)/([0-9]+)/([0-9]+)/(.*)$ /news/post/$4 [L]


2

For your #1, can you browse static files (e.g., put a robots.txt in the root folder) at http://archives.mystie.com? Can you browse http://archives.mystie.com/robots.txt? Make sure that works, as a starting point. From the point of view of EE, it doesn't really know that a subdomain is a subdomain--it's just a domain name / URL. So, in your config file, you ...


2

Yes, it is that easy, I've done this many times. In some earlier versions of Assets I had some issues doing this on a couple of sites, but later versions smoothed out the bumps. As always, do this on a dev copy of the site first - or at the veery least, take a full DB backup first.


2

This may be a mod_security issue. Please check if your host is running it. You can turn off mod_security by adding below code to .htaccess : <IfModule mod_security.c> SecFilterEngine Off SecFilterScanPOST Off </IfModule>


1

I was doing just this last week on a few thousand entries. Assets works really well at converting. First make sure Assets is synchronised with your upload paths. Assets creates a reference to all the files in exp_assets_files. EE File fieldtype stores it's data in the format {filedir_x}your-file.ext, where x is the reference to upload paths config. When ...


1

In summary it is a bit more complex than just copying over the data - there have been some changes in how EE operates internally that require your data to be updated to operate on the latest EE versions. Also the way in which add-ons to EE work changed significantly with EE3, and so it is possible that you will need to change / update some of these too if ...


1

You can find an outline of what is needed in the answer to a similar question asked a few months ago. expression engine upgrade from 2 to 3 to 4 HTH.


1

Never ever do direct EE1 to EE3. First of all upgrade EE1 to EE2. That will make necessary changes to your database. (Remember change all the plugins with EE2 version otherwise backend and/or frontend may crash.) After upgrading it to EE2, upgrade your server then upgrade site to EE3. Remember to: Always take a backup copy of your site. Its good to ...


1

Please consider this question closed. I've turned the site migration over to a more experienced EE developer than me.


1

http://flowingmotion.jojordan.org/2013/07/19/12-steps-to-rebuild-your-wamp-server-without-losing-your-data/ This seems generally useful. Make sure you reinstall the same version of WAMP. Things like your config files and your entire web root are the most important to back up. Make sure you know all of your users and passwords. You can't just make a backup ...


1

When I looked at this about 6 months ago the unfortunate answer was it can't be done :( http://brandnewbox.co.uk/forums/viewthread/666/ They did show interest in adding support but doesn't look to be added yet.


1

RewriteRule ^subdirectory/index.php(.*)$ /$1 [L] This should rewrite your original url: http://domain.com/subdirectory/index.php/segment_1/entry as: http://domain.com/segment_1/entry If that doesn't work, are you able to move your .htaccess into the root of your site directory? Or does it have to stay in your subdirectory? Here is a handy htaccess test ...


1

It might be PHP memory. Try the following in your .htaccess file: php_value memory_limit 128M Updated: If this definitely improves some of them, you might need to keep bumping it up. Try 256M. You're throwing a solution at the problem to see if it fixes it. If so, it's a performance issue in those templates. You can try turning on the Template Debugger or ...


1

This error seems to relate to the use of the master-config methode of setting up ExpressionEngine. I've reverted back to Assets 1 for the time being while this error is being solved bij Pixel and Tonic.


1

I documented our workflow for this in response to "Move ExpressionEngine from development to live", including a link to a video of our git/MySQL steps.


Only top voted, non community-wiki answers of a minimum length are eligible