Publisher does not support the Fluid field type. Please do not contact asking when support will be available.
If you purchased an add-on from expressionengine.com, be sure to visit boldminded.com/claim to add the license to your account here on boldminded.com.
Ticket: Publisher URL prefixes and GMaps Fieldtype issue in CP
| Status | Resolved |
| Add-on / Version | Publisher 1.6.6 |
| Severity | |
| EE Version | 2.10.1 |
Marijan Boljar
Oct 28, 2015
Description:
If Publisher has URL prefixes enabled, then GMaps fieldtype does not load in CP.
If URL prefixes are turned off, then GMaps fieldtype loads correctly.
Gmaps modul used is from Rein de Vries (http://reinos.nl/expressionengine/gmaps/overview) version 3.1.4 and Gmaps Fieldtype 2.1.2
I would not know if this is Publisher or Gmaps issue, but I believe that it is good information for you and Rein, since it is a problem when 2 modules have issues with each other.
I have reported this to Rein and he is currently trying to resolve this in GMaps addon.
Must say that he is really helpfull on this matter, and hopefully will resolve it.
Detailed steps to reproduce the issue:
1. Install Publisher
2. Install Gmaps addon
3. Install Gmaps fieldtype
4. Add field to channel
5. Edit content
Marijan Boljar
Need to add one thing to “Detailed steps to reproduce the issue:”
4.1 Enable URL prefixes in Publisher settings
BoldMinded (Brian)
What is the URL that the fieldtype posts to when in the CP? I’m assuming its doing some ajax requests? Check the network tab and see what URLs are being called via ajax or asset requests.
Marijan Boljar
Will post difference between when URL prefixes are on and off
URL Prefix OFF POST gmaps_act (http://infobip.dev/gmaps_act) - Status 200 POST latting (http://infobip.dev/index.php/gmaps_api/latlng) - Status 200 POST address (http://infobip.dev/index.php/gmaps_api/address) - Status 200
URL Prefix ON POST gmaps_act (http://infobip.dev/gmaps_act) - Status 301 Moved Permanently GET gmaps_act (http://infobip.dev/en/gmaps_act) - Status 200 - ( reponse is : no_method)
Then this leads to JSON parse error for GMaps fieldtype (SyntaxError: JSON.parse: unexpected character at line 1 column 1 of the JSON data)
Like the Gmaps api routes are redirected to /en/ prefix. Was this what you needed ?
BoldMinded (Brian)
If these requests used the normal ?ACT=x requests everything would be fine. I can actually see this method of posting data being an issue for other add-ons as well, not just Publisher. There are others that modify the URL too. I’m not sure if this lies in the Publisher realm of support. It would mean adding special detection for GMaps, which is another 3rd party integration, and I can’t add more 3rd party integrations or it’ll become a cluster of messy code and requiring me to support all these other add-ons.
Are these requests only made in the CP? What does it do on the front-end? What is the referrer of those requests in the network tab?
Marijan Boljar
Off course, I understand this is why I have reported this as “General question” not as Publisher bug. Rein from reinos.nl, maker of GMaps is almost done with fixing all and getting module and fieltype completly compatibile with Publisher.
Hopefully this will be good for all parties involved, users that use GMaps and Publisher, and for both of developers to have modules that work together without problems.
So if all goes ok, soon GMaps and Publisher will work great together.
BoldMinded (Brian)
Good to hear he is adding support. The reason I asked about the referrer of those requests is if I can tell that it came from the CP in anyway, then I could tell Publisher to ignore such requests, thus fixing potential issues with other add-ons, but not adding specific logic for GMaps.
Marijan Boljar
Resolved by Rein. Now GMaps module and Fieldtype are completly compatible with Publisher and all works great together.