Moez Tharani
Forum Replies Created
-
Posts
-
That did the trick, thanks Stiofan.
AH, ok. The location page makes sense then. I’ll sort that out in Widgets.
Regarding “Only GD pages will keep the session”, that doesn’t seem to be happening. If I go and set the location and then immediately go to /places/, which is a GD page, it shows “Change Location” again.
This reply has been marked as private.This reply has been marked as private.This reply has been marked as private.This reply has been marked as private.Ok, that’s what was missing. I knew it was something stupid. For anyone else who runs into this, you have to check Prices and Payment sections and make sure that the “Link Business” is set to “No” otherwise it will link it to a business even if you have not selected that option under Custom Post Types. Thanks again Giri.
This reply has been marked as private.This reply has been marked as private.We have 2 upcoming projects that will use GeoDirectory. Both will launch in a single city, but will eventually support multiple cities spanning multiple timezones. We hired a developer to modify your JSON api to add endpoints that our app framework can read. It was through that process that we discovered the event timezone issue. Our app framework requires timezone information in the time string. We are working around that by hardcoding it in the modified endpoints. But once we start looking at cities in different timezones, that’s going to become an issue.
I feel like timezone support should be bigger than just me though. I certainly wouldn’t want you wasting time fixing something that only one person cares about.
@guust, we are talking about events times and not place times.
Yup, that did the trick! Thanks Stiofan!
This reply has been marked as private.I reverted the change to the compatibility file and inputted your suggestion to the child function.php. It didn’t work. So I’m back to modifying the compatibility file. Thoughts?
So as it turns out, this doesn’t do anything in the geo-1280 function.php:
remove_action('geodir_wrapper_open', 'geo1280_page_title', 10);The only way I can remove the duplicate title is by commenting out this in the compatibility file:
add_action('geodir_wrapper_open', 'geo1280_page_title', 101);Obviously, that isn’t ideal. What’s the right way of doing this?
Alright guys. I get that you’re probably busy and it’s easy to try and dismiss things under the guise of “custom, non-supported”, but I’m paying so that I don’t have to spend hours finding one line of code. And yet, that’s exactly what I’ve been forced to do. After literally hours of going through code trying to figure out what the hell is going on, I discovered this gem in the Genesis compatibility:
add_action('geodir_wrapper_open', 'geo1280_page_title', 101);This makes it so that a duplicate title will appear when you do this:
add_action( 'genesis_after_header', 'geo1280_page_title', 10 );So ultimately, this successfully repositions the title, without a duplicate appearing on the detail page:
remove_action('geodir_wrapper_open', 'geo1280_page_title', 10); add_action( 'genesis_after_header', 'geo1280_page_title', 10 );
