You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The Zip codes admin view does not show saved entries.
I have old entries for Zip codes/ city. The auto populate function for City field by Zipcode works in Checkout, but my Zip code list in admin is empty.
When trying to add a new zipcode in admin is blocked because State is required. For Denmark we don´t use States and the state list is empty.
Please make a state check (hide) on the state field if the country does not use states.
I found the reason for this.
When i update sql table is not created because i skipped version 1.5.0.5.2
So i am missing: sql -> redshop_zipcode -> zipcodeto
When zipcodeto is missing the zipcode list is not listed in backend view. @NguyenBao10 I have mentioned this before that when you do updates it should include all previous deletions and creations if someone skips a version or more like i guess most user do.
Like this
CREATE TABLE IF NOT EXISTS #__redshop_zipcode (
......
..... zipcodeto VARCHAR(255) DEFAULT NULL,
.....
Should then be included in all future version updates here
\component\admin\sql\updates\mysql\XXX+.sql
About the State required check. I can fix this like i did with PR Fix state display none #5608 but i simply can´t find the file where the view is compiled for this
administrator/index.php?option=com_redshop&view=zipcode&layout=edit @NguyenBao10 can you point me to where the file is located?
The Zip codes admin view does not show saved entries.
I have old entries for Zip codes/ city. The auto populate function for City field by Zipcode works in Checkout, but my Zip code list in admin is empty.
When trying to add a new zipcode in admin is blocked because State is required. For Denmark we don´t use States and the state list is empty.
Please make a state check (hide) on the state field if the country does not use states.
redShop 2.1.2.1 and 3.0.3
@NguyenBao10
The text was updated successfully, but these errors were encountered: