Forum Replies Created
-
AuthorPosts
-
poehnix
ParticipantAfter further inspection I found I had a problem with my apache conf.
Fixing it had two consequences:-THE GOOD: now the "Add field" ui interface works again
- THE BAD: all custom fields (in every Field Group) are lost both for edit and exportLuckily enough i had exported them to build 2nd installation.
I guess we can mark the issue as solved.
Thank you
poehnixpoehnix
ParticipantHello,
thank you for your quick response.
Using the custom permalink structure given in the video you linked, the only difference I notice is that the "Loading settings, please wait..." stays visible, while with no permalink the message pops in for a second and than it goes away (without loading the custom fields )
Looking at js Debugger window in Firefox I get the following :Uncaught (in promise) SyntaxError: JSON.parse: unexpected character at line 1 column 1 of the JSON data
For now, to continue developing the site I will use the second installation I have done on my local development machine.
It would anyway be important to have a solution to the problem, should it happen again once the site goes in production.Let me know if you need additional debugging info
Thanks again
poehnixpoehnix
ParticipantFollowup:
I reinstalled everything from scratch, getting php code for moving CPTs and exporting + importing json for Custom Field gruops, so basically using the same codebase in the corrupted and clean installation and that seemed to made the trick but of course this is not the right solution.Now website is empty and under construction. Once it goes live reinstalling and configuring everything from scratch plus importing all the content won't be a choice.
What can I do to make fields / settings appear again, once they are gone ? Might be related to permalink structure change ? This is the only thing I changed (and reverted back once I foound the issue)
poehnix
ParticipantOh too bad! On my testing enviroment I had re-enabled the geolocation plugin!!! I did not find it because I was seeing the ajax queries to nominatim!
Sorry, my mistake. On chrome I got I message that lead me to find the problem.
I confirm the "no message found" is showing correctly
Thank you very much Ahn, and sorry for the trouble
Michelepoehnix
ParticipantNo idea of what's wrong. I am doing some js debugging but I cannot see the value result variable.
Possibly due to the fact that RWMB_Osm.no_results_string is set on line 145 but not on line 190 where there is just a return ?
With a non existent address "XXXXXXXX", clicking on find address does nothing (it correctly does not move the pin on the map but it does not show the message)I am attaching an image too https://imgur.com/sKLkrc7
I am testing it on Firefox, now I will try with Chrome,
Any clue of what is going wrong ?
Thank you
Michele
}poehnix
ParticipantHi Ahn,
I can confirm that now osm map displays perfectly in the frontend.The "no address found" message in the backend does not still display. I have updated meta-box to the latest github release and disabled the geolocation plugin. I have cleared the browser cache too.
When I write an (unknown to OSM) address and click on the "find address" button nothing happens on the map.
Looking at the javascript console I see the ajax request to nominatinm.openstreetmap.org and the response. The response is empty. Where should the message appear? I guess near the address field...
Trying the same address directly in the https://nominatim.openstreetmap.org/ input search reset the map to the whole world.On a side note, due to office relocation I will only be able to proceed with the tests in a couple of days
Thank you
Michelepoehnix
ParticipantHi Ahn,
I have made a bit of testing. I made a new post type with title, editor and osm metabox in code ( osm map + address text field) using metabox from github master branchOn the backend everything seems to be ok. Geolocation works almost fine. The only problem I see is that if the address is not known by openstreetmap, which happens in OSM more than google maps, there is no feedback message (something like "address not found") but, given that markers can be moved "by hand" one can look for another place and then move the marker manually, so it's not a big deal.
On the frontend unfortunately I am not able to display the map. rwmb_meta( 'mapID', $args ) returns an array with the coordinates and zoom value and not the map as expected, something like array(3) { ["latitude"]=> string(10)
"39.7995053" ["longitude"]=> string(10) "18.3579493" ["zoom"]=> string(2) "16" }
I might be missing something trivial here, can you please give me an advice on what I am doing wrong ?One last thing: I had upgraded the geolocation plugin to latest release but I had to revert it back because of some notices on line 73 of geolocation class (types not defined). Probably something related to the geo paramenter. Since geolocation is working, at this point it is not clear if the "geo" parameter (or even the geolocation plugin itself) is needed and / or what one has to put in there.
I will made more tests when I have these info. In the meantime thank you for your hard work.
Bye
Michelepoehnix
ParticipantHi Ahn and David, sorry for the delayed answer.
I will be able to test the code only next week. Anyway, the provided link on github (https://github.com/wpmetabox/meta-box/tree/map-field) returns a 404, so i do not know how to get the code. Ahn, could you please give us the right url ?
I am eager to try the new map&geocoding plugin. Just out of curiosity, is there any reason why you haven't used the Nominatim tools for geocoding that comes with openstreetmap? Reference can be found here
https://wiki.openstreetmap.org/wiki/NominatimThank you for your effort. Next week, once I have the code I will be able to test it.
For the moment thank you for your hard workBye
Michelepoehnix
ParticipantDear Anh thank you for your answer.
I got the eamil too. Google documentation unfortunately is not clear on pricying. They contradict themselves. You can can check the whole thing here https://cloud.google.com/maps-platform/user-guide/pricing-changes/ but I will highlight the key passages in uppercaseQuestion: Can I still use Google Maps Platform for free?
Answer: Yes. Starting June 11, 2018, WHEN YOU ENABLE BILLING, you get $200 free usage every month for Maps, Routes, or Places. Based on the millions of users using our APIs today, most of them can continue to use Google Maps Platform for free with this credit.Question: Can I try Google Maps Platform before deciding to purchase?
Answer: Yes. We want you to experience the speed, accuracy, and comprehensive coverage of Maps, Routes, and Places. YOU NEED A BILLING ACCOUNT TO START, but your first $200 of monthly usage is free, and you can set usage caps to ensure you don’t go over this amount.THE LAST QUESTION /ANSWER IS THE MOST IMPORTANT/CONTROVERT, SO I WONT UPPERCASE THE WHOLE OF IT.
Question: Is a credit card or billing account required?
Answer:Even though your first $200 of monthly usage is free, all Google Cloud Platform services require a credit card and billing account, to cover any amount you spend over this free credit. If you are billed, we'll credit your account for the first $200 of monthly usage. If you choose not to add a billing account, there is a risk that if your usage exceeds $200 in a given month, your Maps API implementation will be degraded or other API requests will return an error. If your estimated usage will be above $200 a month and you don't have a credit or debit card to set up a billing account, a local Google Maps Partner may be able to help.The first sentence says a credit card is compulsory. The second sentence says you have a choice.
According to my understanding Google says it's up to his grace to let your keys function and who, when and for how long continue to support any single key.
The main reason for this is that stopping all the free services for all at the single time will mahe google loose potential customer. Probably they will "kill" keys that generate a fair amount of traffic saying "Hey, I told you I would have done this", leaving all the low traffic keys, maybe adding a bandwidth limit to slow them down.Can we afford this uncertanty ? These days some services I use that are based on google maps started working awkward. It might be a coincidence, but I read this of a wanted threat of the times to come.
The key point here is that, given the type of clients I have, I cannot ask for their credit card details. 11th of June is round the cornder so, at least to me, adding openstreetmap (or other) support with geocoding should be a priority
Sorry for the long post. Thank you for the time spent to read it. I think a lot of developers are in my position right now.
As always, thank you for your work and the excellent support you provide for your extensions.Sincerely
Michelepoehnix
ParticipantIt worked!
Thank you very much
Bye
Michele -
AuthorPosts