I am attempting to upgrade my version of drupal from 6.20 to 7.0. When i try to get to update.php page, i get this error before I even can start the update script:
DatabaseSchemaObjectExistsException: Table role_permission already exists. in DatabaseSchema->createTable() (line 630 of /var/www/drupal/includes/database/schema.inc)
Anyone know how to fix this (without removing any tables from my database)?
Drupal.org has a multi-page tutorial on upgrading from Drupal 6 to 7. You can check it out here: http://drupal.org/documentation/upgrade/6/7. I would suggest following that as closely as possible.
Related
I am using Drupal 8.6.7. Now I am getting below message.
There is a security update available for your version of Drupal. To
ensure the security of your server, you should update immediately! See
the available updates page for more information.
https://www.drupal.org/project/drupal/releases/8.8.1
How to apply above security patches although not using 8.8.1?
The documentation states :
Versions of Drupal 8 prior to 8.7.x are end-of-life and do not receive
security coverage.
The only solution to apply these patches is to upgrade core :
If you are using Drupal 7.x, upgrade to Drupal 7.69.
If you are using Drupal 8.7.x or below, upgrade to Drupal 8.7.11.
If you are using Drupal 8.8.x, upgrade to Drupal 8.8.1.
I just installed Dspace 4.2. I added some items. But when I access the Community, collection or item statistics in the JSPUI view it does not show any value to me.
Any help ?
Thanks in advance.
if it is a fresh installation I strongly suggest to use a more recent version. My recommendation is to use dspace 5.10
https://github.com/DSpace/DSpace/releases/tag/dspace-5.10
that is the best one in terms of stability, otherwise you can try dspace 6.3
Anyway, the latest version of the 4.x series is the 4.9 https://github.com/DSpace/DSpace/releases/tag/dspace-4.9
The issues is probably due to issue in the SOLR statistics core but without additional information, logs file, is difficult to guess. Take a look to what is logged in the ${dspace.dir}/log/dspace.log ${dspace.dir}/log/solr.log when you access the statistics page
I have upgraded Kentico site from Kentico 8.2 to Kentico 9.0, everything was looking pretty and working smoothly. But when I tried to export my own site, I got Exception with following statement.
“Conversion failed when converting from a character string to unique identifier”.
From your current description it is impossible to tell what might have broken. The exception you are getting is very common and you can find many examples of reason why it happens here in SO.
However, what might be related to your question in Kentico is whether the upgrade you performed was successful. Try checking CMS_SettingsKey table for following KeyNames
CMSDBVersion
CMSDataVersion
Are they both set to 9.0? If not, the upgrade was not entirely successful. If yes, then there is some other issue within the data in your database for which we would need much more information.
Some of the class form definitions haven't been upgraded properly. Try the upgrade again and make sure you perform all the Steps after upgrade, especially "Running the website - First request".
I need to upgrade my solr search from 4.7 version to 5.3.1 .
I am working on a linux platform.
Can you please provide me the steps that i need to follow .
Thank you!
I do not think that there is a definitive step by step guide for the upgrade that you are looking for.
I have a 4.3.x SOLR running in a production environment and I am contemplating the leap to upgrade to 5.x. However its clear that a lot has changed and that my upgrade is not going to be straight forward.
Also other priorities in my project have kept me from doing the upgrade.
So rest of the discussion is more a thought process than actual upgrade experience.
Last I researched I found the below links useful
https://support.lucidworks.com/hc/en-us/articles/203776523-How-to-upgrade-between-major-Solr-Versions
https://cwiki.apache.org/confluence/display/solr/Major+Changes+from+Solr+4+to+Solr+5
From the Major changes link you will notice that a lot has changed ..
Most notably there are changes to the index format, SolrJ removal of deprecated API and that the deployment is now as a standalone server instead of a war file.
So I would suggest that you ask yourself the following questions ...
Is it possible to recreate the index from scratch ? How much time does it take to create your complete index ? If your index can be recreated quickly then , I would suggest that you do that using 5.x engine on a separate machine, while your production environment is served by your existing server. Then plan a complete upgrade from 4.x to 5.x by simply pointing your Production instance to the new SOLR engine. This approach will give you a clean slate to start with and a brand new index (but with existing data).
If you have a very large index (e.g. it takes several days to recreate it from scratch), then you may want to perform an upgrade of the live index. In that case I suggest that you consider the following.
The SOLR upgrade guide mentions 4.10 as a version that is 4.x (so I assume its is easy to upgrade from any 4.x to 4.10) and has some features built in to help with the move to 5.x. So first upgrade to 4.10 ensure that your index continues to work properly. Then use the guides mentioned above to upgrade to 5.x
I've been trying to work through an issue that developed while attempting to upgrade our testing environment from 12.04 to 14.04 ubuntu on aws. Prior to this, the Package repository version of solr was 1.4.1 which matched our 1.4.1 solrj client integrated with our application.
Changing the base AMI to the 14.04 latest and running our default deploy caused solr 3.6.2 server to be installed. It appears it was accepting our configs without issue, however when our client tried to connect we received different errors:
The first was an unknown custom field, which we traced back to our deployment scripts not moving our schema.xml and solrconfig.xml to /etc/solr/conf/ but keeping it in the base directory.
We corrected this issue, and then ran into the following:
'exception: Invalid version or the data in not in 'javabin' format'
This was generated by a wrapper ontop of solrj, but I'll be honest and say I know nothing regarding Solr and that this may be on our end. I've asked our dev team to look at 2 options:
1) enabling: 'server.setParser(new XMLResponseParser());'
Which is the recommendation on the backwards compatibility for an older client.
2) updating our client in the application to 3.6.2
-I know less about the requirements on this.
My fall back is to revert to 1.4.1, but it appears it hasn't been touched since 2011, which makes me hesitant.
Any thoughts / suggestions would be appreciated!
Thanks!
I think the best option is to maintain the same version of Solr and Solrj.
I used for a lot of time Solr 1.4.1 and, while as you said, the most part of it works with newer versions without any problem, actually a lot of things have been changed since 1.4.*
I did your same porting last year, (from 1.4.1 to 3.6.1) and I can confirm you that the 2nd way is the right one: all changes you must do in your client code are just "formal" and very very quick.
Any workaround you could do for being able to communicate with a different version (between Solrj and Solr) is just, as the word says, a "workaround" and it could lead to unexpected (hidden) side-effects later.