Navigation problems with prev/next and "find events"

Hi,
I’m having a similar problem with “next/prev month” links.
I noticed that the the url of that link has a double slash,
e.g.: https://www.example.com//events/2015-01/
In fact, if I digit the url with a single slash, it works.
Thanks for your help.

Update: I partially solved the problem, as I had wpml plugin activated but I hadn’t translated the event yet.
However now, when I click on “january”, I don’t see immediately the page of the following month. I see it only if I reload the page…

Hi Squazz,

Thanks for your post. I’m sorry you’re having trouble. Have you tried deactivating other plugins to look for a conflict, or switching to a default theme like Twenty Twelve? If you need help, please read this guide to testing for conflicts.

If you can isolate this as an issue that’s inherent to The Events Calendar, we’d be happy to look into it further. Unfortunately, we can’t help troubleshoot conflicts here on the free forum. If you do find a conflict, you can try getting in touch with the developer of the theme or plugin and see if they can shed some light on the issue.

We also have some resources that might be helpful for you in troubleshooting a conflict:

? Themer’s Guide – provides an overview of how to customize the plugin’s frontend appearance.
? Tutorials – useful tips and tricks for changing how the plugin looks and behaves.
? Technical Docs – provides an overview of the classes and functions in each plugin

Good luck, and thanks for using The Events Calendar!

~Leah

Hi albe67,

I’m sorry, but our plugin is not currently compatible with WPML or similar multi-lingual plugins. It’s possible that the issue you are still seeing is related.

We are hoping to make TEC compatible with WPML in the future. If you’d like to stay updated, add your vote to the UserVoice page. We’ll update there as we go.

Best,
Leah

I found the problem. It’s the theme.
I got in touch with the developer (me) and he doesn’t know what the problem could be.

I have tried to look through the links you posted, and I didn’t seem to find what my problem could be. Do you guys have an idea for where I should start?

I found the problem.
To get jQuery Accordion to work at my site, I had to insert the following code in my footer:

<!–noptimize–>
<script src=”//code.jquery.com/jquery-1.10.2.min.js”></script>
<script src=”//code.jquery.com/ui/1.11.1/jquery-ui.min.js”></script>
<!–/noptimize–>

When deleting the “jquery-1.10.2.min.js” line, everything works again. The problem is then, that my accordion stops working :/

By queening jQuery accordion this way

wp_enqueue_script('jquery-ui-accordion');

I could delete the following code:

<!--noptimize-->
<script src="//code.jquery.com/jquery-1.10.2.min.js"></script>
<script src="//code.jquery.com/ui/1.11.1/jquery-ui.min.js"></script>
<!--/noptimize-->

This solves my problem with TEC’s dependency on jQuery and my bad theme setup ??

Still, I see it as a problem that page navigation is dependent on JS.

I am supper happy you got it working Squazz. Your solution in the end is definitely best practice, good call.

> Still, I see it as a problem that page navigation is dependent on JS.

I don’t completely disagree. There are a few reasons for that. One of them is SEO. We have issues where conflicting themes or ironically SEO plugins like to override our robots noindex meta, which harms sites at times. Other reasons to. But, if you would like to see it not be dependent upon JS, please put that in a feature request: https://tribe.uservoice.com/admin/forums/195723-feature-ideas Even I would vote that one up.

– Brook

Becuase you are an admin, you link is broken. For future users, the correct link is without the admin part: https://tribe.uservoice.com/forums/195723-feature-ideas

I have now posted a suggestion here: https://tribe.uservoice.com/forums/195723-feature-ideas/suggestions/6833539-js-independent-page-navigation and encourage everyone interested in seeing this feature “JS/jQuey independent page navigation” implementet to come by and vote ??

Thanks Squazz, that was my bad.