EEC.MS - ExpressionEngine add-ons

*Please read update instructions.

Ok team, 1.1.0rc is a released. It’s RC, since I did some important changes in a core and I want you to pay a little bit more attention during the testing. An update takes some time because of choosing some wrong directions during the custom field’s integration. But now I have a lot of opportunity to improve functionality in the future .

So, what has been done for today:
1. Custom field support – added a number of fields, you needed,  to describe the point. At the moment you can use only text input, but I’m going to update it for the next versions (I’m developing it parallel with another ext. which works with custom fields too).
2. Info Windows & Sidebar creating opportunity.
3. Simple SEAF – creates markers based on address.
You can find examples in documentations.

what will be ready for next release (in one week):
1. SAEF map (at this moment you can used simple SAEF);
2. All Global setting will moved to module page;
3. Custom field’s auto fill base on google map request (so you will have possibility fill automatically fields address, city, zip etc.);
4. Direction support;
5. Custom fields ordering;
6. Markers list and custom ordering;
7. Order search results by distance;

     

I’ve just updated to 1.1.1 rc and am getting these errors (see attachment)  when I load a publish or edit page.

     

Hi,
just to confirm Paul’s report… the same here.

     

Hello,
Could you please reupload the package? Thanks!

     

Updated and now get attached errors.
Looking at my database the mx_google_map_fields table only contains 3 fields (address,city,zipcode) and line 347 is looking for ‘state’.
So it looks like my existing field have not been updated with changes in the fieldtypes.
Do I need to remove the module and fieldtypes and re-install?

     

my mistake - I forgot to make changes for auto Map function. Please reupload the package. Also, if you need to recreate mx_google_map_fields you just need to uninstall module (without fieldtype) and install it again (1.1.3rc). But its really strange that this fields was not created.

     

That stopped the errors, but things were not right.
I was getting {state} showing in the slide out box field for State.
I tried editing an existing point and when I saved it I lost the all pin data for that entry with errors about the fields.
I still think I have problems with the fields in the database.

I can’t spend any more time on this for a few days so I think I will just uninstall it all and start again when you release the next version.

     

Thanks to Max going into my Control Panel, it’s all sorted now.
Now to start thinking about the new possibilities this addon opens up.

     

Thank you for your work on this add-on!

I just want to let you know: While uninstalling there is an error because in line 99 in the file upd.mx_google_map.php the table name is wrong: “ee_mx_google_map_fields”.

     

After saving an entry with a map location pin saved, if you edit that entry the map is not centred on the pin you saved but a bit off to one side. There must be some reference to the pin location though, as it is not the same for every entry or the default centre that you defined in the settings.

Any ideas when the next version will be available?
I have just started work on a new site and would like to use this, but I am aware this is still beta, and the site will go live in about 10 days.

     

Hi Paul - next version will be avalible this week.

     

Any news on the new version?

     

Sorry team - my project where I used this add-on was on hold all October, looks like now it’s ok, so I planed to release to new version over the weekend. A lot of bug fixing, finally couple new filedtype support ( + filemanager support) + templates for auto matched fields from google map api. Also I rewrite the locator part, so it will work with more functionality.