Hey all - another plugin spawned by a site I’m working on. I needed a dropdown list of countries and a combined dropdown of US states and Canadian provinces in a couple of spots on the site. Rather than using two or more plugins to do this, I decided to spend some extra time and try my hand at the one regional dropdown plugin to rule them all. 😊
REEgion Select will display a dropdown <select> list of:
See also the FieldFrame version for use in the EE control panel.
Insipiration from - and props to - Nathan Pitman’s UK Counties Select (where I got the list of counties from) and US States Select plugins, and Bridging Unit’s Countries Select plugin.
Just thought I’d let everyone know that I finally got REEgion Select ported to FieldFrame, for those of you looking to use it via the back-end rather than on the front-end.
Thanks for the solid start on the lists, D-Rock. I’m currently developing a site where I’ll need the client to select a state or country within an entry post, that will then be searchable through the same parameter (the 2 digit code) on the front end.
I just installed the FF back end version, but whenever an entry is saved, it defaults to the last list item. Do you know what this may be from? Any thoughts?
I also just noticed if I include the pre-populated list for the front end while having the FF back end fieldtype list setup for a custom field, it throws the following error:
Fatal error: Call to undefined method Reegion_select::usage() in .../plugins/pi.reegion_select.php on line 9
Is one not meant to be used with the other? This is my first time working with these files, so I could very well be approaching it incorrectly. My thought process is if I were to select “Texas” for the entry’s state and publish it, I should just as well be able to search for Texas on the front end and have that entry display in a results page; in other words both plugin and fieldtype working together.
Can you point me in the right direction?
Thanks for catching those bugs, I appreciate it. I’ve just pushed version 1.0.1 to GitHub, which should fix both of these issues.
I had to rename the class to Reegion_select_ff to avoid the conflict with my REEgion Select plugin, which means the name of the fieldtype folder has changed as well. You’ll want to first remove the version 1.0 fieldtype, then upload the 1.0.1 version. You may have to revisit your custom field setting as well to choose REEgion Select again (but don’t worry - your existing entry data will remain unchanged.)
Let me know if the update sorts this out for you?
Hi D-Rock,
Great plugin, perfect for my ecommerce sites where I have to use ISO countries to pass to the payment gateways - many thanks.
Some additions needed for the UK Counties list: “West Midlands” - had a client complain as one of their customers from that county tried to purchase and couldn’t enter their address! “Sussex” isn’t actually a county, it’s two: “East Sussex” and “West Sussex” Like East and West Lothian.
Have added these in manually, but thought I should give you a heads up.
Another change request: I’ve got 2 ecommerce payment gateways that require a 3 digit country code based on ISO, so any chance the plugin could be modified to allow a choice in the back-end of which ISO standard is used for the list? I can provide a ready to use list of countries and 3 digits if it helps?
Thanks,
Peter
Could you please add North Lincolnshire and North East Lincolnshire to the UK Counties?
I don’t see these on the Wikipedia listing, nor the Association of British Counties list.
Looks like it’s a Borough, not a County?
Packet Tide owns and develops ExpressionEngine. © Packet Tide, All Rights Reserved.