Dirk
Forum Replies Created
-
Posts
-
Nope, I have not that requirment or the expectation.
A user “save” is okay for me as I can implement something around. But no autosave. If you like to have this function, I need a switch to turn it off.
What does in the long run here means?
I need two options at two different sites:
1) Default: /[CPT-slug]/[place-name/slug]
2) Full location: /[CPT-slug]/[country slug]/[region slug]/[city slug]/[place slug]
I’m not using neighbourhoods.In case of SEO I see an advantage with solution one because if readability of the urls at the SRPs.
For the test I’m getting 404 switching to “Full location”:
1) Go to places
2) Go to any detailed place page
3) Click on Places again
–> 404 with a wrong created linkDirk
Stiofan,
I need here something that will not store any personal data (like the IP) for this function.
In my environment the $_SERVER variable is returning localhost for any users because of GDPR. Too many plugins are storing personal information without asking someone or describing it in the documentation. This function will not work in my environment anyhow.
The message and also the filling of the fields needs to be disabled.
I have mentioned this before that this is against my privacy policies.What do you mean?
If I’m setting it to “default” GD permalinks I can click as often as I can on the place in a listing, but the detailed page is not opening.
If I switch to “Full location” I can open the place detail page, BUT now one “/” is missing in the link behind the “/place” so I’m getting an error.
Also the plugin is not respecting the location home URL and always try to send me to a location oriented page instead of “/”. I have no location switcher on and it looks like that the URL generation tries to do something of a preselected location.
Plugin has been tested for over 5 weeks, few bugs are to be expected.
I was just wondering as all people starting to test the LMv2 are running in the same problems directly after installing the plugin.
See pic
oops. no, the same as in my installation. lol.
On the above mentioned site it looks even a little bit more out of place.
“Hour” is too low. and still overlapping.
This reply has been marked as private.The timezone of the server is defined as UTC, but this should not make a difference.
This reply has been marked as private.The pull request of Kiran is still open
yup, it is this
I’m on Win10 and tested it with Chrome 68 and same on Edge 42.
This is coming out of the sample data
In your shared screen you can still change the default location after the merge. If you click multiple times all locations are deleted, but the places are not touched.
