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.
Related
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.
There are some bugs in django-registration0.8, that's why it installed 0.9 version manually throw ssh and also places newer version of registration directly near my scripts (under registration folder). However, django still users an old version. I'm trying to source ..\virtaulenv and then pip uninstall that package, but get Permission denied error.
What would you recommend me?
That should have worked. Here's a forum thread that walks through a quick example of uninstalling django (fist comment): https://www.openshift.com/forums/openshift/socjalregistration
If it's still failing, can you post your steps to reproduce the error and the error itself? Feel free to use the forums, or follow up here.
Please help!
I have an installation of magento v 1.5.1 and I want to upgrade it to 1.7 but when i try to
list upgrades, this is what i only see:
wp_theme_grayscale: 1.0.7 => 1.4.0
RicoNeitzel_VertNav: 0.3.1 => 0.4.0
Locale_Mage_community_fr_FR: 1.7.0.0 => 1.7.0.1
TBT_Enhancedgrid: 1.3.2.1 => 1.031
any suggestions?
after upgrading all,
and tried to list all upgrades again,
it couldn't see any upgrade anymore.
your help would be much appreciated.
EDIT:
I used this guide. http://turnkeye.com/blog/magento-upgrade-guide/
I did not get any error. the updates above are just the updates that i can see,
OK, I can share my successful experience of upgrading:
Go to System -> Magento Connect -> Magento Connect Manager
Log in using your username and password
Click on “Check for Upgrades” button
4.You will notice that most package rows turn to yellow. These packages are the only that have available updates. Go to each package row, click on “Actions” drop-down menu and select the most current stable version available.
Note: Stable version available may vary for each package. For example, some packages may have 1.7.0.2 upgrade version and others 1.7.0.1 or lower. Don’t bother with this, just pick the latest stable version available.
When you are done selecting upgrade version for all packages, click on “Commit Changes” button.
Now, you have to wait. Give it some time. During upgrading process, you may see various notes or outputs that may be tricky and you may think that the process is done. Well, IT IS NOT. Just wait, give it some more minutes. The process will be done when there is no activity in the “command line” like console for about one minute.
Click on “Refresh” button. You are almost done! Technically, you have completed the upgrade process.
Go to your cPanel file manager or your FTP client and delete EVERYTHING in var/ directory.
Last but not least, reindex data in Admin -> Index Management
When you enter admin section and scroll down, you will notice that it says “Magento ver. 1.7.0.2”
This process worked for me fine.
Please try to run
./mage list-upgrades
In some cases there might be no Mage_* entries in the list. In this case the following command can be used:
./mage install http://connect20.magentocommerce.com/community Mage_All_Latest --force
I got it working now.
what i did is after the upgrade, i re uploaded my database back up, and viola the error is gone. The error has a hint, and yes because of duplicate thing that it could not continue if the table already exist.
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.
This one has been driving me nuts for a few days now and I've tried Google but no luck (judging from my good luck with finding answers on google, this is a rarity for me not to find an answer).
To cut a long story short, I did have the capability to compile my mxml files via the browser on my local machine. I've had to do a reinstall but now I'm having problems trying to compile.
My current setup is:
WAMP 2.0i
- Apache 2.2.8
- PHP 5.2.8
- MySQL 5.1.36
FlashDevelop 3.0.0 RC1
Win XP
I've tried compiling in Firefox 3.5, IE8 & Chrome but all receive the same error:
Compilation results
Errors, warnings or exceptions were found while compiling null.Visit the online Flex documentation or API reference for further information.
An error occured on the server. Server error is: 'Error occurred in server thread; nested exception is: java.lang.NoSuchMethodError: flex.license.License.(Ljava/util/Map;Ljava/lang/String;Lflex/license/Logger;)V'
I've followed the instructions from adobe:
http://labs.adobe.com/wiki/index.php/Flex_Module_for_Apache_and_IIS
but no luck. I can compile without an issue via CMD but I prefer to use the browser as I find that much faster. Has anyone run into this issue and solved it?
Cheers!
DNT
Edit:
I forgot to mentioned I've tried using the Flex 2 & 3 SDK to no avail.
I believe I can safely say I've answered my own question.
Rather than using a program to clear out the registry (eg ccleaner), run the uninstall on the "flex module for Apache & IIS" then do a reboot.
Once you get back into windows, 'stop all services' in wamp and check that your httpd.conf file has removed the entry:
#BEGIN FLEX INSTALLER EDITS - REMOVE ONLY ON UNINSTALL
LoadModule flex_module "D:/your/path/to/modules/mod_flex.dll"
AddHandler flex .mxml
#END FLEX INSTALLER EDITS - REMOVE ONLY ON UNINSTALL
Now go wild and run the 'flex module for apache & IIS' installer, answer the questions and when you get to the end, do the reboot and it should work.
What a PITA!
I FINALLY found the answer!
Got a new pc for work so I had to reinstall everything and I've found the solution that worked flawlessly.
Use this link to download the Adobe Flex SDK which is over 100MB; ignore the Open Source Flex SDK download links. At the time of writing, I downloaded version 3.4.0.9271:
http://opensource.adobe.com/wiki/display/flexsdk/Download+Flex+3
Make sure you follow the Installation Instructions up until the To install the Flex module heading.
http://labs.adobe.com/wiki/index.php/Flex_Module_for_Apache_and_IIS#Installation
Then go to this page and under the main heading Flex 3 Compiler Modules then under the sub heading 3.0.0.477, download the file FlexModule_apache.exe and follow the installation instructions and you should be home free!
http://opensource.adobe.com/wiki/display/flexsdk/Downloads