magento2 – Magento 2.3.1: Postal code of the billing / delivery address automatically removes leading zeros

We have an issue where the billing / shipping addresses of an order automatically remove the leading 0 from a zip code. For example:

Danbury, Connecticut, 06811 becomes Danbury, Connecticut, 6811

This leads to some validation errors with UPS and other shipping APIs that are trying to validate 6811 as zip code.

How can we make it so that the invoice / shipment stores the full zip code with a leading zero?

Software installation – install Ruby 2.3.1 – Ubuntu 19.10 – Build failed

I am new to the Ubuntu and Ruby installation and the Linux installation in general.

I get the following issue when I try to install Ruby 2.3.1 via rbenv. Any idea why that could be? Many thanks.

prem@chinz:~$ rbenv install 2.3.1
Downloading ruby-2.3.1.tar.bz2...
-> https://cache.ruby-lang.org/pub/ruby/2.3/ruby-2.3.1.tar.bz2
Installing ruby-2.3.1...

BUILD FAILED (Ubuntu 19.10 using ruby-build 20191124-2-g77e949a)

Inspect or clean up the working tree at /tmp/ruby-build.20191205111801.21317.gjqU1A
Results logged to /tmp/ruby-build.20191205111801.21317.log

Last 10 log lines:
make(1): *** (exts.mk:208: ext/openssl/all) Error 2
make(1): *** Waiting for unfinished jobs....
linking shared-object objspace.so
make(2): Leaving directory '/tmp/ruby-build.20191205111801.21317.gjqU1A/ruby-2.3.1/ext/objspace'
linking shared-object date_core.so
make(2): Leaving directory '/tmp/ruby-build.20191205111801.21317.gjqU1A/ruby-2.3.1/ext/date'
linking shared-object nkf.so
make(2): Leaving directory '/tmp/ruby-build.20191205111801.21317.gjqU1A/ruby-2.3.1/ext/nkf'
make(1): Leaving directory '/tmp/ruby-build.20191205111801.21317.gjqU1A/ruby-2.3.1'
make: *** (uncommon.mk:203: build-ext) Error 2

magento2.3 – Magento 2.3.1 :: Orphan attribute records

Recently we had a problem with the number of files in the pub/media/product/cache Folder that causes us to run out of inodes.

In our research, we found many duplicate images in the folder. Hoping to remove them, we used this extension to remove only a few images.

Since there were many images that did not belong to products, we found it strange that so few pictures were removed. Here the real problem (or part of it) was discovered.

In that catalog_product_entity_varchar There are references to these images in the table, but the entity_id for these records does not match entities in the table catalog_product_entity,

I think that's why the extension mentioned above did not delete the duplicates because they were considered to be used by these defunct entities.

So the real question is why these records were not removed when the product was deleted. And why were the pictures also left on the server?

For now, I think I'll run a query to remove the orphaned records from the attribute table.

delete from 
    catalog_product_entity_varchar att 
where 
    (select 
         count(*) 
    from 
        catalog_product_entity 
    where entity_id=att.entity_id) = 0

So in summary:

  • Why are the attribute records removed when the entity is deleted?
  • Why do the product images stay behind when a product is deleted?
  • Is it safe to run the above query to delete these records?

The upgrade from 2.3.1 to 2.3.3 has been done. The billing address drop-down menu no longer appears on the checkout page

I hope to get some light on the subject here. After updating from 2.3.1 to 2.3.3 via Composer, you can use the drop-down menu in the frontend during the checkout page in the area where the user will change the billing address by unchecking "My billing and delivery address equals" with The billing address is no longer displayed.Payment method section screenshot

This behavior affects all payment methods that require a billing address. I tried to turn off my one-page checkout, and the behavior is the same. I contacted the one-page developer, and he told me that the problem is most likely related to the creation of themes or static files, but that no error log is displayed in system.log or in the exception, because the Problem persists .log. The theme is the default luma theme, no changes.

However, a warning appears on the Chrome web console checkout page:
Enter image description here

I have no idea where the mistake could be. I tried switching from production mode to developer mode, redeploying static content, clearing the cache, and clearing the cache, but everything does not seem to work.

The commands I did for the upgrade were:

php bin/magento maintenance:enable
composer require magento/product-community-edition=2.3.3 --no-update
composer require --dev allure-framework/allure-phpunit:~1.2.0 friendsofphp/php-cs-fixer:~2.14.0 lusitanian/oauth:~0.8.10 magento/magento-coding-standard:~3.0.0 magento/magento2-functional-testing-framework:2.4.5 pdepend/pdepend:2.5.2 phpmd/phpmd:@stable phpunit/phpunit:~6.5.0 sebastian/phpcpd:~3.0.0 squizlabs/php_codesniffer:~3.4.0 --sort-packages --no-update
composer update
bin/magento cache:clean
rm -rf var/cache/*
rm -rf var/page_cache/*
rm -rf generated/code/*
bin/magento setup:upgrade

Thanks for any help in advance.

[Vn5socks.net] Car Update 24/7 – Good Socks 10h50 PM

LIFE ~ 166.62.85.161:23127 | 0.246 | Unknown | Unknown | Unknown | Unknown | Checked for vn5socks.net
LIFE ~ 66.148.119.241:9300 | 0.224 | Unknown | Unknown | Unknown | United States | Checked for vn5socks.net
LIFE ~ 64.90.48.72:10070 | 0,151 | Brea | CA. | 92821 | United States | Checked for vn5socks.net
LIFE ~ 166.62.123.35:25689 | 0,267 | Unknown | Unknown | Unknown | Unknown | Checked for vn5socks.net
LIFE ~ 95.179.162.82:32365 | 0.27 | Unknown | Unknown | Unknown | Greece | Checked for vn5socks.net
LIFE ~ 192.169.215.114:53497 | 0.252 | Unknown | Unknown | Unknown | Unknown | Checked for vn5socks.net
LIFE ~ 64.90.48.43:43500 | 0.158 | Brea | CA. | 92821 | United States | Checked for vn5socks.net
LIFE ~ 188.134.77.205:7779 | 0,322 | St. Petersburg | 66 | Unknown | Russian Federation | Checked for vn5socks.net
LIFE ~ 184.178.172.13:15311 | 0,324 | Unknown | Unknown | Unknown | United States | Checked for vn5socks.net
LIFE ~ 103.51.15.108:30003 | 0.024 | Unknown | Unknown | Unknown | Unknown | Checked for vn5socks.net
LIFE ~ 178.62.233.112:9780 | 0.256 | Unknown | Unknown | Unknown | Russian Federation | Checked for vn5socks.net
LIFE ~ 50.62.57.97:37768 | 0.411 | Scottsdale | AZ | 85260 | United States | Checked for vn5socks.net
LIFE ~ 13.231.110.249:1081 | 0.12 | Norwalk | CT | 06850 | United States | Checked for vn5socks.net
LIFE ~ 104.238.97.215:57869 | 0.437 | Unknown | Unknown | Unknown | Unknown | Checked for vn5socks.net
LIFE ~ 220.79.34.109:2018 | 0.083 | Seoul | 11 | Unknown | Korea, Republic of | Checked for vn5socks.net
LIFE ~ 80.211.71.44:7008 | 0201 | Unknown | Unknown | Unknown | Denmark | Checked for vn5socks.net
LIFE ~ 136.244.81.26:30766 | 0.283 | New London | CT | 06320 | United States | Checked for vn5socks.net
LIFE ~ 95.179.245.60:33086 | 0,255 | Unknown | Unknown | Unknown | Greece | Checked for vn5socks.net

Feuerhimmel
Reviewed by Feuerhimmel on
,
[Vn5socks.net] Auto Update 24/7 – Good Socks 10h50 PM
LIVE ~ 166.62.85.161:23127 | 0,246 | Unknown | Unknown | Unknown | Unknown | Checked at vn5socks.net
LIVE ~ 66.148.119.241:9300 | 0,224 | Unknown | Unknown | Unknown | United States | Checked at vn5socks.net
LIVE ~ 64.90.48.72:10070 | 0.151 | Brea | CA | 92821 | United States | Checked at vn5socks.net
LIVE ~ 166.62.123.35:25689 | 0,267 | Unknown | Unknown | Unknown | Unknown | Checked at vn5socks.net
LIVE ~ 95.179.162.82:32365 | 0.27 | Unknown | Unknown |

Rating: 5

,

[Vn5socks.net] Car Update 24/7 – Good Socks 10h25 PM

LIFE ~ 167.99.68.43:9000 | 0.047 | Fort Worth | TX | 76104 | United States | Checked for vn5socks.net
LIFE ~ 70.168.93.218:17026 | 0.32 | Santa Barbara | CA. | Unknown | United States | Checked for vn5socks.net
LIFE ~ 166.62.58.161:2649 | 0.423 | Unknown | Unknown | Unknown | Unknown | Checked for vn5socks.net
LIFE ~ 47.101.56.1:1088 | 0,254 | Ottawa | ON | k1y4h7 | Canada | Checked for vn5socks.net
LIFE ~ 139.180.211.29:1088 | 0,044 | New Kensington | PA | 15069 | United States | Checked for vn5socks.net
LIFE ~ 80.211.71.44:7008 | 0.214 | Unknown | Unknown | Unknown | Denmark | Checked for vn5socks.net
LIFE ~ 192.169.249.15:14667 | 0,329 | Unknown | Unknown | Unknown | Unknown | Checked for vn5socks.net
LIFE ~ 124.65.145.126:7302 | 0.265 | Peking | 22 | Unknown | China | Checked for vn5socks.net
LIFE ~ 136.244.81.26:30766 | 0.292 | New London | CT | 06320 | United States | Checked for vn5socks.net
LIFE ~ 13.231.110.249:1081 | 0,124 | Norwalk | CT | 06850 | United States | Checked for vn5socks.net
LIFE ~ 95.179.162.82:32365 | 0.286 | Unknown | Unknown | Unknown | Greece | Checked for vn5socks.net
LIFE ~ 95.179.245.60:33086 | 0.316 | Unknown | Unknown | Unknown | Greece | Checked for vn5socks.net
LIFE ~ 70.168.93.201:17009 | 0.31 | Santa Barbara | CA. | Unknown | United States | Checked for vn5socks.net
LIFE ~ 72.221.164.35:60670 | 0.31 | Unknown | Unknown | Unknown | United States | Checked for vn5socks.net
LIFE ~ 167.71.146.116:9050 | 0,271 | new York | NY | 10020 | United States | Checked for vn5socks.net
LIFE ~ 103.51.15.108:30003 | 0.024 | Unknown | Unknown | Unknown | Unknown | Checked for vn5socks.net
LIFE ~ 5.9.157.99:60473 | 0.286 | Unknown | Unknown | Unknown | Germany | Checked for vn5socks.net
LIFE ~ 82.165.137.115:7061 | 0.274 | Unknown | Unknown | Unknown | Germany | Checked for vn5socks.net

Feuerhimmel
Reviewed by Feuerhimmel on
,
[Vn5socks.net] Auto Update 24/7 – Good Socks 10h25 PM
LIVE ~ 167.99.68.43:9000 | 0.047 | Fort Worth | TX | 76104 | United States | Checked at vn5socks.net
LIVE ~ 70.168.93.218:17026 | 0.32 | Santa Barbara | CA | Unknown | United States | Checked at vn5socks.net
LIVE ~ 166.62.58.161:2649 | 0,423 | Unknown | Unknown | Unknown | Unknown | Checked at vn5socks.net
LIVE ~ 47.101.56.1:1088 | 0,254 | Ottawa | ON | k1y4h7 | Canada | Checked at vn5socks.net
LIVE ~ 139.180.211.29:1088 | 0.044 | New Kensington | PA | 15069 |

Rating: 5