Forum Replies Created
Thank you, Dylan.
Ticket has been submitted.
That is substantially better. Even solves the table overflow issue that I was going to bring up if I couldn’t address it myself.
I still would like to see a dropdown option for mobile, but understand that will have to wait for some dedicated coding.
Thank you very much!
PS – May want to sticky this for others looking for a cleaner mobile layout.
This is in my PHP error log:
Parameter must be an array or an object that implements Countable in /www/wp-content/plugins/wp-google-maps-pro/includes/custom-fields/page.custom-fields.php on line 33
I would also like to point out one more oddity. Regardless of browser, if I input whatever into a custom field for a marker, save the marker and then save the map, the data entered appears on the front end map marker listing as it should.
However, whatever was input into those fields is not displayed in the marker settings after saving although it is obviously in the DB. I think this is something that should be fixed. What is the point of putting into a custom field if it appears that nothing has been input and saved?
And one more issue. As an example:
1. I create two custom fields (location and phone).
2. Edit a marker, input a locaton but fail to input phone. Save Marker. Save Map.
3. Frontend shows location as it should, but obviously not a phone number since that was left blank.
4. Edit marker again, inputting the phone number, save marker, save map.
5. Now the phone number is displayed on the front end but the location is now empty.
6. So apparently all custom fields have to have data input before saving – everytime – even if only needing to update a single custom field such as a phone number.
So, while I appreciate the inclusion of custom fields, their implementation has apparently not been thoroughly tested.
Strangely, I am not getting any errors using FireFox Developer Edition version 67.0b12 – just a blank result. Tested with an older version of FF (50.1.0) with the same result.
However, I just tried with Chrome hoping it would return an error and it worked! So it something specific to FF. Tested and working in Safari as well.
I do not have any extension in the FF Dev Edition that would prevent JS calls, routines, etc. In fact I don’t ave any extensions installed in that version at all.
Even more interesting is that if I successfully add custom fields via Chrome or Safari and then do something as simple as click “save” in the custom fields section with either of the FFs, the fields are removed.
Please do. As you know, mobile devices will certainly be the primary method of web access in the near future and already is in many parts of the world. Therefore, devs absolutely must be considering mobile UX design of their products as a top priority.
I have privately sent you the link. However, while CSS may help some, I believe the functionality of the default pagination will never truly be mobile friendly, especially for sites like the one I am referencing that contain large numbers of locations in the DB.This reply has been marked as private.
I too am having the same issue. When I click “add” after filling everything out I get asked if I want to stay on the page or leave the page. No matter the selection, no custom field is added. Same if I click save instead of add.
Plugin version 7.11.21 and Pro version 7.11.27