Magento 1.9.3 - I created a custom module for add attributes in customer account.
Since last one year I am upgrading using same module but now when I am trying to upgrade mysql4-upgrade-0.1.9-0.2.0.php it's not working.
core_resource database version is 0.1.9
Cache i have already cleared
Same upgrade script is working on development server
Issue has been resolved. Due to the cache problem new version was not updating but after clear cache multiple times it's working.
Related
I am new to shopify CLI and trying to run shopify theme pull or shopify theme serve but cannot due to an error I keep on running into
PS C:\Users\Russell\shopify\shopifyApp\starter> shopify theme serve
Your environment Ruby version, 3.1.1, is outside of the range supported by the CLI, 2.6.6..<3.1.0, and might cause incompatibility issues.
X An unexpected error occured.
To submit an issue include the stack trace.
To print the stack trace, add the environment variable SHOPIFY_CLI_STACKTRACE=1.
ive tried to downgrage ruby to 3.1.1 using gem update --system 3.1.1 but get this in my cmd
C:\Users\Russell>gem update --system 3.1.1
ERROR: rubygems 3.1.1 is not supported on 3.1.1. The oldest version supported by this ruby is 3.3.3
im using windows 10 and ruby 3.3.3
Well I managed to get a solution and what I did was :
This happens because when you create a Development store, it won't properly link your Shopify Partners account to the new created store.
A partial solution was mentioned here #1309 (comment)
This is what I do to solve the problem on my side:
1.- Logout from the Development store admin dashboard
2.- Login again by visiting the direct URL. Example: https://[store-name].myshopify.com/admin
Here use your Shopify Partners account (the one that you used to create the development store). Don't worry if you see an error message or if you have to login again. Ideally you should see the admin dashboard again.
4.- Login to your Shopify account (not Partners). Go to: https://shopify.com/login
At this point you should see the new Development store listed. This means it is now linked to your account.
Go back to the CLI and try again. You may have to do shopify whoami and/or shopify logout shopify login
github solution to the problem
Using Magento 2.2.1 freshly installed
I use php 7.1.1
I am using Adyen payment gateway
https://github.com/Adyen/adyen-magento2
the extension developer says its not due to their extension. I have enabled every php extension on server side thats needed. So now it comes to magento 2
Tried to checkout as guest and then I see
Failed to load resource: the server responded with a status of 500 (Internal Server Error)
https://{siteurl.com}/rest/default/V1/guest-carts/1a41b8daeba4d90df7c5dca2085dd732/payment-information
When I try to use COD or Check the checkout process is smooth. Haven't tried with paypal or others
**Can you please help ??
If you need me to perform any steps in either server side or magento 2 please tell me the steps on what to do I will post the output here**
I have solved the issue
Solution : I used a third party extension and installed it through magento 2 admin directly which resulted the extension was not installed properly. I have used composer to install the extension and it solved the issue
I work for Adyen.
It is indeed required to install the Adyen plugin on Magento through Composer. This will include all the dependencies and prevent the issue that is shown here.
For further references you could visit our Github page:
https://github.com/Adyen/adyen-magento2
Hope that it helps!
For the unexpected error (e.g 500), we should enable error reporting on the bootstrap:
app/bootstrap.php
ini_set('display_errors', -1) // enable this line remove # from start.
you will get the real issue on screen
I'm trying to install Magento 1.8, however I got stucked in configuration step.
I got the following message: 500 Internal Server Error
Looking log file I could verify the following:
SQLSTATE[42S01]: Base table or view already exists: 1050 Table 'eav_entity_type' already exists"
But, here is the problem because it is a new installation and this table does NOT exist.
My Products versions are: W32 (test environment) PHP 5.4 MySQL 5.6.14 Magento 1.8.1.0, IE 9 FF 25.0.1 Chrome 31.0.1650
Could you please help me? Thanks a lot.
Login to your database using phpMyAdmin and make sure there are no tables in there.
If there are, drop the user/table and re-create it anew and re-try the install wizard.
Just delete all tabels or re-create databbase, and start installation again.
Today I finally got it. I did a totally new installation on Debian amd64. I installed only LAMP softwares and probably the FastCGI was avoiding to get success. It is necessary to confirm this.
In my store have magento community edition - 7.1.
I try to install extension using magento store, but I got an error like this for all type of extensions
community/Dropifi_Dropificontactwidget: Could not resolve host: connect20.magentocommerce.com; Host not found
I placed this key for install magento
http://connect20.magentocommerce.com/community/Dropifi_Dropificontactwidget
http://connect20.magento-commerce.com/community/Dropifi_Dropificontactwidget
Help me to get a result for this issue.
Thanks
I had the same problem ("CONNECT ERROR: Unsupported resource type") while upgrading a 1.6 magento on PHP 5.5.
The unpack function (http://php.net/manual/en/function.unpack.php) has changed.
In downloader/lib/Mage/Archive/Tar.php, the line
const FORMAT_PARSE_HEADER = 'a100name/a8mode/a8uid/a8gid/a12size/a12mtime/a8checksum/a1type/a100symlink/a6magic/a2version/a32uname/a32gname/a8devmajor/a8devminor/a155prefix/a12closer';
must be replaced by:
const FORMAT_PARSE_HEADER = 'Z100name/Z8mode/Z8uid/Z8gid/Z12size/Z12mtime/Z8checksum/Z1type/Z100symlink/Z6magic/Z2version/Z32uname/Z32gname/Z8devmajor/Z8devminor/Z155prefix/Z12closer';
This was not an issue specific to you. Today, the Magento Connect server experienced an outage which prevented any of the community extension keys from working.
The Connect server appears to be online now, so try again and it should work.
Source: https://twitter.com/magento/status/384805097315659776
Helpful Note:
You can download extension packages directly by using the following tool:
http://freegento.com/ddl-magento-extension.php
Just paste in your Magento extension keys and Submit. A downloadable link will appear for you to obtain the package.
i have got this error then try following steps
first you can disable all cache
second after install extension then clear all cache and logout and login
I have been upgrading a joomla (2.5- to - 3.1) site locally but the upgrade is broken. The sql upgrade did not pass. I have been trying to use the database fix option but even like that did not get it to work in my case.
Database schema version (2.5.11) does not match CMS version (3.1.1).
Table '#__content' does not have column 'title_alias' with type 'VARCHAR(255)'. (From file 1.7.3-2011-10-15.sql.)
I have been trying to execute manually the other query but fails.
How could I fix my broken tables?
Where could I get a valid sql upgrade script?
Try clicking the "Fix" button on the Extension Manager > Database view. If this still does not resolve your issue, you'll need to manually apply all of the fixes. You can grab the SQL updates from GitHub (the same relative file path applies as well) and manually run each file's queries using a tool such as phpMyAdmin. Note you'll need to change the table prefix (#__) to match that of your own site.
had the same problem when doing upgrade 2.5.11 => 3.1.1, fixed it by first using phpmyadmin to add a title_alias field with VARCHAR(50) to #__contents table.
after which joomla added another complaint that title_alias should not exist in 3.0.
After applying 'Fix' I guess the old update scripts for 1.7 first changed title_alias to VARCHAR(255), then the update for 3.0 removed it again, updated the schema version in the db
and joomla stopped complaining...
Hope this helps you.