I am quite the newbie as far as Drupal dev goes. I've been asked to upgrade the core version of an existing website.
I used composer to update the drupal/core package and its dependencies, cleaned the cache, ran the database updates, which went rather smoothly...BUT...
Some of the blocks are not displayed anymore
Autocompletion in fields does not work anymore
My drop-down selects are not displayed (the values they are using are loaded properly)
I have no idea why this happens.
Any hint, anyone?
Thanks!
Related
I’ve greatly re-written my plugin and have revamped an upgrade process. I would like to test if it behaves as I expect it to behave when someone updates to this version.
Therefore, the question is, is it possible to force my development website to show a link to upgrade to trunk or even better specific tag (without changing version in repository) of my plugin so that I can test it?
In case someone needs this as well.
According Samuel Wood (Otto/Otto42) to there is Plugin Beta Tester which lets you download and install trunk version or tag with a higher version (I've tested this one).
Since you don't update readme.txt in trunk, users do not get prompted about new version and repository doesn't get updated either so you can fully test new version of the plugin, from start to end without worry about someone getting it before time.
I just installed the module "Date" and after enabling drupal gave me the error: Enable Date API first, so i enabled the Date API and then the Date module and now drupal crashed and it says "Page not found" and i dont have any menu in the admin panel.
Menu rebuild does not work, i created an script for it without result
Restore from your most recent backup which you should have made before installing a new module. ( Note:Drupal is not for amateurs, despite what they say. Drupal does not have professional governance, like say Wordpress, and that makes it relatively demanding for the inexperienced. With Drupal you really need to be sit next to a helpful pro for a year.)
Check that the version of PHP , Drupal, MySQL and the Date module are all compatible. This is work, BTW. If not compatible, then reinstall where necessary and cross your fingers.
Check for known issues by Googling something like or based on "Drupal 7 Date module". Drupal 7 is old and issues that have arisen with so-called compatible modules may be well-documented.
I fixed it by restoring my sql backup. Not a good fix but yea...
I have decided to update my development PC to use PhpStorm-2017.1, but before I update, I do not want to end up wasting 1-2 days re-configuring, if there are any potential issues that can hinder my work.
Will my current license work on the new version?
Will my project settings integrate with the update? (Symfony)
Will my plugins settings be kept? (Symfony)
Any other thing I need to figure out?
Answers to your questions:
1) Yes, the new installed version will automatically pick up your current license.
2) When you update, only the software is updated. The configuration files are not touched and settings are brought across as they were on the previous version.
3) Same answer as answer # 2
4) Not really. Just download the latest version from their website and install it as you would normally.
upgrading to phpstorm 2017.1 was smooth for me, (once they released some later fixes for things like the REST tool etc)
As for your plugins, it'll depend on what plugins they are, and whether there would be BC breaks. Look up the plugin documentation and check to see if there's a version for 2017.1.
For what its worth, the symfony plugin works fine.
You can try official control panel of JetBrains https://www.jetbrains.com/toolbox/app/
Manage product updates with ease
The pace of technologies and software updates is ever-accelerating. Stay up-to-date without compromising your productivity with the Toolbox App: easily maintain several versions of the same tool, install updates, and roll them back instantly if needed.
Could be useful to patch instead of complete update:
Faster updates
When updating, Toolbox App downloads and applies a patch (or even a set of patches) instead of the full package download, thus saving you time & bandwidth.
Official response form JetBrains:
It's hard to tell whether your plugins will work with 2017.1 since there are always some changes in API that may affect some of your plugins. So it's easier just to install 2017.1 and see how it goes. Installation won't broke your existing PhpStorm 2016.2 and its settings.
I believe there have been no changes in license server so if you have right on 2017.1 there shouldn't be any problems.
P.s. Thank you every one for your responses. I will be going with the official answer.
I'm developing a Tool using Symfony 2. Since my Version of Symfony is a bit old, I would like to update. My current installation is the one "with vandors" and I'm using it under Win7 with XAMPP.
I feel somehow stupid, but even after searching the internet for over an hour, I didn't figure out how to update correctly to Version .15
You would be a great help, if you could give me some dumb-secure instructions on this, because all I've done so far to install or patch software was running an exe-file.
Hopefully my english was good enough to point out what my problem is, but nethertheless I excuse myself for all mistakes.
Greetings GrimReaper1908
The update steps are always given in the release announcement (see Symfony 2.0.15 released):
If you already have a project based on the Symfony Standard Edition
2.0.x, you can easily upgrade to 2.0.15 by getting the new deps and deps.lock files. Then, run the vendors script (it also clears your cache):
./bin/vendors install
If you modified deps file to include additional vendors you'll have to manually merge it with the latest Symfony one.
Vendors script requires git client to work. You'll have to install it.
Since you're on windows: Symfony2 installing vendors in Windows
Last week I had released a version of a WordPress plugin that works if the user was doing a fresh install, however if they already had the plugin and upgraded it using the WordPress upgrade automatically feature, problems occurred and some of the database elements were erased. So I had to revert back immediately.
I was wondering if there was a way to test the plugin through the upgrade automatically functionality before hand instead of having to release it and hoping you get it right the first time.
I would set up a dev/local site running the previous version of your plugin. Then, copy over the latest changes (overwriting all of the files) and test things out.
In essence, that is the same thing that happens during an automated upgrade.