Forum Replies Created
-
AuthorPosts
-
Steven Zahm
Keymaster@ Karine
Not sure what you are asking … I only pointed out that code as the potential source of the conflict since it seems to occupy the same namespace as the jQuery Slider. You’d have to the theme dev to see if this is indeed the source and ask if they could make it so it does not conflict with jQuery Slider.
Keymaster@ Brett
Yes, I received it. I ran out of time yesterday and did not get thru all my email. I’m catching up today so I’ll be responding soon.
Apologies for the delay!
ps. here’s the link to the other thread, not disappeared ;)
http://connections-pro.com/support/topic/create-searchable-field/
Keymaster@ Brett
Well, it seems Google is actually now requiring the browser and server keys starting June 22 for new sites:
https://googlegeodevelopers.blogspot.co.za/2016/06/building-for-scale-updates-to-google.html
That’s really sad! At least one positive is that OpenStreet Maps will finally get a lot more attention and focus. So it should relatively quickly finally be a real alternative.
Any way…
A few days ago I did add support for the browser key. I can email an advance copy of the next release, planned for later this week. It’d be great if you could test it just to make sure the browser key does fix the issue.
Let me know.
Keymaster@ Schulz
I do not have any hotmail address for you that I am aware of so no worries there :)
I just sent the beta to the email address you use to make your post. Hope that is the right one!
Keymaster@ Karine
I do not think the conflict is in the HTML markup. I think it is in the javascript. It hard to tell though because there are no console errors being shown and there is a heck of a lot of javascript … that’s why I’m guessing
Since you were able to narrow the conflict down to the jQuery Slider library used by Hours my guess is that the javascript for the theme’s header slider just happens to use the same name to init it’s header slider. Look at line 1214 in the theme’s script.js file. jQuery Slider is registered with the exact same name. Since Hours loads just about dead last it would “overwrite” the existing slider.
That guess seems to make sense now. When looking at the page prior to removing jQuery Slider, the broken header showed what looked like a button in the upper left. I’m guessing that was actually a jQuery Slider control.
07/01/2016 at 10:14 am in reply to: Two versions of directory with different category groups visible #381130Keymaster@ Carolin
I’m actually working on a project right now with very similar requirements as far as the category searching. There is one category that only logged in members should be able to search by. Hiding two categories (or more) can be done quite easily. My suggestion would be to have only a single directory though. You can put the search box in a “public” and “member” page and when a search is performed, the results page will be the same directory page. Hope that makes sense!
Keymaster@ Matt
Alrighty, I’ll leave this open until I hear back!
Keymaster@ ottomek
In theory, yes, filters and actions could be added to support the export of the custom meta fields. I have not tried this yet so code tweaks might be necessary in order to ensure support.
Let me know if this is something you decide to pursue.
Hope that answers your question!
ps. I’ll be in touch via email about the CSV import of your meta in regards to the our other ongoing project shortly.
Keymaster@ Raymond
Great to hear! Hope you run into no issues :)
Keymaster@ Karine
The jQuery Slider is a core WordPress script.. Perhaps the theme includes it’s own conflicting version or uses the same “namespace” for its header slider as jQuery Slider uses. If the later is the case, the jQuery Slider would overwrite it which would cause the header slider to stop working. This is just speculation. Either way, I believe the source of the conflict is the theme.
-
AuthorPosts