I am a newbie in this arena. Due to project demand, I had to install the newest version of Confluence. So, I have taken the backup and install confluence 6.12 on top of 6.6. After completing the installation when I hit the URL I have got the following error message.
Roll back the instance by restoring the backup you made prior to attempting the upgrade. Do this by creating a fresh Confluence install (I would recommend using the same version of Confluence that you used to create your XML backup). Restore the XML backup to this.
Get that site working normally first.
Then connect to a supported database.
Proceed with the upgrade.
Related
I want to modify the logstash integration rabbitmq plugin and use it
(https://github.com/logstash-plugins/logstash-integration-rabbitmq.git)
I modified the inputs/rabbitmq.rb and confirmed that it works properly on my local.
I created an offline pack to upload it to the server, but the modified contents are not applied to the offline pack.
No errors when installing gem files or creating offline packs
After installing as an offline pack, when I checked rabbitmq.rb (vendor/bundle/jruby/2.5.0/gems/logstash-integration-rabbitmq-7.1.0-java/lib/logstash/inputs/),
the file modification time seems to have changed, but the modifications have not been applied.
I don't know why it can't only be applied to offline packs
How do I fix this problem?
I Solved this problem using JRuby.
Before Ruby was installed on my local, and I used it for building gem.
After changing JRuby, the offline pack is ok.
I'm trying to get Magento 2.4 running using the production ready zip and I keep getting it to this point where I believe it's ready to start the setup process, but it's waiting for me to agree to the ToS. Unfortunately there's no agree button or instructions on if there's a file I need to edit. I just did a fresh install of XAMPP with PHP 7.4 and still have the same issue, and can't find a similar mention on google.
Is there supposed to be an agree button, do I need to edit a file?
Term & Agreement link leads here, still no agree button. Getting started link takes me to installation instructions for a Linux CLI
I saw I may still need to run the composer install command even on Windows, but I was under the impression the production ready zip already had the dependencies included. Where am I going wrong??
Update: I got composer running in windows terminal and it returns that there is nothing to install.
According to the official site docs, in a note at the top of the installation instructions for a CLI install of Magento 2.3:
"The Web Setup Wizard is being deprecated in Magento 2.3.6 and will be removed in Magento 2.4.0. After it is removed, you must use the command line to install or upgrade Magento."
So you cannot install Magento 2.4 without touching the command line.
I've tried every method I can think of to update from 3.1.5 to 3.2.3 and each time it pretty much kills my site and leaves me with the error:
Fatal error: Call to undefined method JLoader::registerAlias() in /homepages/.../libraries/cms.php on line 61
At which point I just clobber the rest of the site and reinstall my backup (oh man you GOTTA LOVE Akeeba).
I've upgraded Joomla successfully and unsuccessfully about 100 times over the past few years on various sites and this is the first time I'm stumped as how to move forward.
One interesting piece of data is in the Admin Control Panel of the 3.1.5 is that the Joomla version says "Unknown" even though the System Information lists it as 3.1.5.
So, anyway, what is the ABSOLUTE, BLESSED method for moving from 3.1.5 to 3.2.3? If I should simply be able to install the 3.2.3 upgrade zip file then I guess I'm toast. In that case, what would happen if I left the database as is and cleared out all the files and then installed the 3.2.3 full stable package? Would that work?
Do you have Akeeba backup installed? You need to make sure it is updated first before updating joomla.
So if yo have a back up, restore that, update Akeeba, then update Joomla again.
http://www.rockettheme.com/forum/general-discussion/215394-pressing-the-joomla-update-button-killed-my-site
The solution was pretty easy, though unexpected. See here.
Error in file:
/usr/local/sites/client/magento_site/app/code/core/Mage/Customer/sql/customer_setup/mysql4-upgrade-1.4.0.0.7-1.4.0.0.8.php" - SQLSTATE[42S01]: Base table or view already exists: 1050 Table 'customer_form_attribute' already exists
I tried upgrading this using this tutorial from turnkeye to go from 1.4.1 -> 1.4.2 and then to 1.6 but after all the mage upgrading was complete, when I hit the website to upgrade the database I get errors about database tables that already exist and it appears to be running a database upgrade script for a version of magento before 1.4.2. I know this error is extremely common and I have seen many blogs posts about it and read all that I have found -- I see no resolution besides starting a fresh install.
I've heard people say this can happen if a previous upgrade didn't complete successfully but I don't think that is the case here -- I think it was a fresh install at 1.4.1 (at least I don't believe I ever upgraded it). Anyone know why this is happening or how to fix it?
Note 1: I also tried the upgrade by overwriting the 1.4.1 files via SSH with successive version of magento -- always the same database errors though. If I remove the mysql-upgrade script that is failing, then another one fails in its place with a simliar 'table already exists' error.
Note 2: I also made sure I cleared /var/cache and /var/session and even tried reindexing. No success.
Looks like it is just complaining about a table already existing. Either install a fresh version of you database from before you tried to upgrade then clear cache and sessions and try again
Or
Just open the file referenced and temporarly comment out the part that is installing the table again. That should allow you to by pass the error.
Then you can download the magento Database Repair Tool to ensure that your tables are correct.
But all I get from my Connect Manager is the following message:
community/Mage_GoogleShopping: Version for 'Mage_GoogleShopping' was not detected
If I try and use the version 1 extension key all I get is:
Couldn't resolve host 'magento-core'
I am using a mostly fresh install of Magento Community 1.5.0.1 (I say mostly because we do have our own template but it is very basic).
Anyone have any luck installing this extension. GoogleShopping is a huge boon to our hit count and the recent changes to the google products API has really affected our implementation.
this extension is still in alpha stability, you need to change your preference settings ("settings" tab in your magento connect manager) for "preferred state"
OSdave had the right answer ... but the way I fixed the error message was I blew away the download folder on the server and re-copied over from the original Magento install package.
Once I had done that I re-ran the Extension Key in Connect and this time it actually said. "That Extension is in Alpha stage. You'll need to change your preferences to install it."
I did NOT get the error above anymore. At that point everything worked like a charm.