addressfinder / addressfinder-woocommerce Goto Github PK

Why have you removed the changelog from both here & the official plugin repo?

Site operators need to know what's changed with each version.

The Magento plugin code is currently all minified in the browser, which makes it difficult for anyone except us to debug it. This is not great for open source.

A good solution is to use sourcemaps. This is a special file that connects a minified/uglified version of an asset to the original authored version. You can set this as an option for webpack. There is no performance hit because sourcemaps don't get loaded unless you have dev tools open. This would make it easier for both us and other users to debug 🎉

There are three steps

1. Export the non-minified addressfinder-webpage-tools package by. This file can be minified by the plugins themselves.
2. Add sourcemaps to the webpack config of each of the plugins.
3. Deployment. There may be some trial and error here

@nigelramsay do you have instructions for how to create a new Wordpress test server?

@1mattramsay @josephleniston, just fyi I have moved this card up from the backlog because I tried our plugin on the new wordpress/woocommerce and there is a small styling bug which should be fixed as part of this story.

Hello, AddressFinder!

WordPress 5.5 is scheduled to be released on August 11th. Are your plugins ready?

After testing your plugins and ensuring compatibility, it only takes a few moments to change the readme "Tested up to:" value to 5.5. This information provides peace of mind to users and encourages them to update to the latest version.

Here are the current "Tested up to:" values for each of your plugins:

• https://wordpress.org/plugins/addressfinder-woo/ (tested up to 5.3.4)

For each plugin that is compatible, you don't need to release a new version — just change the stable version's readme value.

Looking to get more familiar with 5.5? Read this roundup post on the core development blog to learn more about the varous changes coming to core with this major release:

https://make.wordpress.org/core/2020/07/30/wordpress-5-5-field-guide/

There are six areas that specific focus should be given as plugin-related changes coming in 5.5:

1.) Note the version of jQuery shipped in core will be updated in 5.6 and as a first step jquery-migrate is no longer enqueued by default in 5.5. Updates to your code are required if you rely on jquery-migrate or .live() to function properly as they are being removed. You can verify this by checking your code with WP_DEBUG enabled to make sure you are not using deprecated code. Please do this to avoid unnecessary support requests and negative reviews for your plugin:
https://make.wordpress.org/core/2020/06/29/updating-jquery-version-shipped-with-wordpress/

2.) Note the new plugin auto-update UI and how to ensure your plugin is ready for the new auto-updates system:
https://make.wordpress.org/core/2020/07/15/controlling-plugin-and-theme-auto-updates-ui-in-wordpress-5-5/

3.) Note the Block Directory guidelines (https://make.wordpress.org/plugins/2020/07/22/proposed-block-directory-guidelines/) and how to get your block plugin added to the Block Directory:
https://make.wordpress.org/plugins/2020/07/11/you-can-now-add-your-own-plugins-to-the-block-directory/

4.) Note the new XML sitemap feature and how it can be integrated with your plugin:
https://make.wordpress.org/core/2020/07/22/new-xml-sitemaps-functionality-in-wordpress-5-5/

5.) Note the deprecated $HTTP_RAW_POST_DATA global variable in the PHP related improvements & changes devnote:
https://make.wordpress.org/core/2020/07/14/php-related-improvements-changes-wordpress-5-5-edition/

6.) Note the various plugin recommendations in the miscellaneous changes devnote:
https://make.wordpress.org/core/2020/07/29/miscellaneous-developer-focused-changes-in-wordpress-5-5/

In order to ensure compatibility, you can download and beta test your plugin with the latest WordPress version here: https://make.wordpress.org/core/handbook/testing/beta-testing/

Thank you for all you do for the WordPress community, and we hope you enjoy 5.5 as much as we do.

WordPress core contributors

The addressfinder-webpage-tools package has recently been updated to version 1.6.0. The changes are listed here:

https://github.com/abletech/addressfinder-webpage-tools/releases/tag/v1.6.0

The current version in use is 1.5.1.

This update should be applied to the addressfinder-woocommerce project.

Test that the new behaviour (change to clearing of fields) works well, and then create a new release.

Originally reported by @ronjali.

Customer Feedback - known issues of the WooCommerce plugin

Here are some issues that customers recently have reported regarding the plugin.

1. AddressFinder plugin looks strange inside WP/WooCommerce
Our plugin appears to 'look strange' on the WooCommerce/Settings/Payments page. Existing customer contacted us and wondered why the AddressFinder plugin appeared on the payments page (which it's supposed to). Could be related to recent changes by WooCommerce.

2. 'Save changes' button disappear
A new customer was unable to save the settings on the WooCommerce/Settings/Payments page. The 'Save changes' button was gone. This means that the customer was unable to save the changes after entering his licence key, and was therefore unable to start using AddressFinder.

When the user deactivated the WooCommerce Payments plugin temporarily, the AddressFinder 'Save changes' button did appear and he was able to save the changes.

The user was using:
WP Ver is 5.8.1
WooCommerce version is 5.7.1
Woocommerce Payments Ver 3.1.0

(Ref: https://app.hubspot.com/live-messages/20223507/inbox/1726336352#email-reply-editor)

3. NZ users can't choose country in the plugin

https://addressfinder.nz/docs/plugins/woocommerce/

NZ users don't have the option 'Default country' inside the plugin settings, like the Australian plugin does.
This results in free plan customers getting error messages returned when their user is entering an address of the other country in their checkout.

Example from AU plugin:

4. Drop down address suggestion box disappearing

We've had a couple of recent WooCommerce customers reporting on this issue recently.

• "Hi there I've recently added address finder to my website and I'm having some issues with the drop down address suggestion box appearing while address is being typed but then it's disappearing before you can select the address.
  thelocalbunch.com.au
  My website is using Wordpress ver: 5.8.1 Woocommerce ver: 5.6.0 Plugin ver: 1.4.6".

• "Hi, I’ve installed the plugin on a client’s website and testing it and realised that the address suggestion box tends to appear briefly when typing in the address and disappears before one could click on it. What would have caused this issue and how can I rectify that? https://doesprinkles.com.au/checkout-page/
  The site is running on WooCommerce 5.6.0 and Wordpress 5.8.1."

Could this search both the address and points of interest datasets at the same time?

For some addresses like hospitals and schools it seems like people don't know the street numbers so fail to get matching address in the address dataset alone.

A particular example from our users: Wellington regional hospital. Officially at 39 Riddiford St, but according to the DHB and everyone that seems to work there the address is just Wellington Regional Hospital, Riddiford St. The hospital is in the Points of Interest dataset and so we could populate the address from that matching just wellington regional hospital if it was searched at the same time as the address dataset.