53

I know your method works flawlessly, but it scares the crap out of me. Luckily Craft's update setup is magical. What I do is this. Make sure my repo is clear of unstaged files, just so the update can be in a commit all by itself. Run the update on my local dev environment (with a local database) (Test) Commit the updated files and push Backup live ...


15

I actually keep all the craft system files gitignored. This way, all the assets are independent of the version of Craft and therefore of the updates. When it's time to run an update, I'll do it on dev first and then I'll run it in production knowing that it'll be fine. So far I have not had a problem with this approach and it seems to me that it is a more ...


11

I personally use a slightly different method than what Jeremy recommends. Clean repo on the git side of things: no unstaged or non committed files Backup live DB and import in dev Update dev (test) Update production Commit & deploy Not encountered any problem so far and Craft runs its tests on both environments.


10

Make sure both Craft installs are up-to-date. Craft's license is saved in craft/config/license.key, make a backup of your purchased license file. Move all your files/directories except: /craft/app/ /craft/storage/ Copy the backup of your license.key to craft/config/. Remove /craft/storage/, if it exists on your new server, to prevent cache errors. "...


6

You should receive an email after purchasing a Craft license. Maybe double check your email details and/or your spam folder. Anyway, if you email the guys at support@buildwithcraft.com they will sort out a receipt for you.


6

We have multiple clients, and so using craft.dev for our development is not really feasible. How about client1.craft.dev, client2.craft.dev etc?


5

To update plugins like SeoMatic, just download the latest (either clicking on the direct download link from the /admin/updates/ page in your admin area or from github). Then you just then need to upload the new folder, overwriting the old one, to your server in the /craft/plugins directory (make sure you rename the download to seomatic as before, removing ...


5

As of a few weeks ago we added a "proper" PDF invoice attached to the receipt email that works for most people's cases. We don't currently capture anything like your company information during the checkout process, so if you need that on the invoice, or you placed your purchase before we started attaching the invoice, hit us up at support@buildwithcraft.com ...


5

The good news is, 2.4 isn't that old. The bad news is, 2.5 was one of the most significant updates Craft has ever seen. For that reason, you'll want to exercise a little more caution than you typically would need to. To begin with, backup your database! I can't emphasize this enough... you want to make sure that you have captured a "moment in time" for your ...


5

In my specific case - upgrading from 2.0.2551 to 2.1.2570 - the issue was caused by there being millions of rows in the craft_entryversions table. One of the migrations in the update needed to loop through every row in that table and do something to it and therefore it took ages. Simply emptying that table solved the upgrade process for me. Caveats ...


4

In additional to Lindsey's excellent answer, I find a lot more comfort in updating Craft than WordPress. P&T spent a lot of time making sure the one click updates just work. Unlike WordPress, Craft will make a backup of your database before it updates so if anything goes south, it can revert back automatically, though on a big version jump like this, ...


4

You can add: 'aliases' => [ 'siteUrl' => 'http://yoursiteurl.com', ], To your config/general.php or use: 'aliases' => [ 'siteUrl' => getenv('DEFAULT_SITE_URL'), ], And define DEFAULT_SITE_URL in your .env file (better way).


4

1) Is there anything to say about a release date for Craft 4? And about around what time Pixel and Tonic consider it a stable release to be used in production? Nothing official on either. 2) What will happen to the support and updates for Craft 3 once Craft 4 is out? Is there any roadmap showing support/update-cycles for Pixel and Tonic products? No ...


3

I'd want the client knowingly and enthusiastically on board with a sensible plan that'd support business goals and the nature of evolving software. Either a) do with fewer plugins/integrations, b) invest in privately upgrading the plugins, c) open source the work if possible and ask for improvements with fingers crossed, or d) rethink the site so it's less ...


3

Your purchase on the "real" domain was tied to your the craft/config/license.key file on that site. All you should need to do is move your files up except for your local development license.key file, restore the database to the production site and adjust any domains/paths as necessary.


3

To answer my own question: There may be some plugin incompatibilities when upgrading to Craft 2.5. This is to be expected, given all the variables. In my case the Placid plugin was not yet compatible, as seen when I put Craft into devMode. So either: Wait on the upgrade until your plugins are current, or Disable lagging plugins as necessary if you need ...


3

That should do it! Auto-updating to 2.5 is causing a few people headaches, mainly because people are bumping up against their php.ini setting limitations. It's a pretty significant update, requiring pretty significant server resources to handle the transition. Once you've successfully rolled back, I'd recommend performing a manual update. This takes a lot ...


3

Based on your comments, I'd recommend creating a new entry type in your section. Create a "Redirect" entry type which only contains a URL link (or an Entry field) so the page knows how to handle the redirect. For any entries that need to be converted to a redirect, simply swap the entry type to use this instead. Then you can simply map that entry type to a ...


3

So far, Craft 3 hasn’t had any “real” breakpoint releases in the way that Craft 1 and 2 had, yet – where you would have a real issue if you were to update past them before updating to them. Craft 1 and 2 had a handful of them, which we took as opportunities to clear out the migrations/ folder, and clean up some PHP code. If you were to (somehow) update past ...


2

Thanks to carlcs for pointing this out. If I edit the Standard.json file in craft/config/redactor/ as per these instructions (https://craftcms.com/help/redactor-ii-configs) it's fixed. I find it odd that Craft 2.5 didn't come with this Redactor config fix included, rather than letting it break and leaving it up to developers to fix it. I can understand if ...


2

I was having a similar issue and found a solution that worked for my setup: https://craftcms.stackexchange.com/a/9016/831


2

It was a bug. Brad fixed it. Working now.


2

Go to the Settings page (/admin/settings - reached by clicking on the gear icon at the top right of the control panel) and you should see the following link at the bottom of the page: Click on the Show me link and the modal window pops up.


2

Updated using composer update craftcms/cms


2

Craft is going to have a better update system in a version 3. With Seomatic you can also be able to update via composer. As far as I know.


2

Matt's answer covers some good ground, especially this line: "Odds are they chose Craft and their custom plugins for a reason and those reasons are still vitally relevant, as is the ability to stay nimble in the future." Wanted to expand on some points... I've walked into these kind of building-on-fire situations before and it's important to figure out the ...


2

The issue appears here $isConsoleRequest = Craft::$app->getRequest()->getIsConsoleRequest(); if (!$isConsoleRequest && !Craft::$app->getUser()->enableSession) { return null; } For whatever reasons Craft::$app->getRequest()->getIsConsoleRequest(); does not return true -> !false becomes true -> it tries to grab the user which ...


2

Those aren't so much errors as deprecation messages, meaning you should fix them sometime before Craft 4 comes out where they'll be going away and become real errors for you. :) To which I assumed I should just add 'securityKey' => 'xxxxxx', but the error hasn't gone. They won't go away automatically. Go to yoursite.com/admin/utilities/deprecation-...


1

You can use this article to help debug 504 Gateway Timeout errors that can be common when updating Craft, because those tend to be longer running operations: https://craftcms.com/support/504-gateway-timed-out-error Your solution works because PHP timeouts from the command line are generally much more forgiving that PHP timeouts from a web browser. Craft 3 ...


1

After doing some more digging in storage/logs, it turns out that the permissions were incorrect on the "cpresources" director. Once I fixed those, the upgrade progressed as normal.


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