Print all Events on one page/List

[Jessie]

Hello,

We’ve been running into problems with the “Next” and “Previous” links on the events list. With our security setups, unauthenticated users are not able to click the “next” and “previous” buttons because of the call to admin-ajax.php.

In looking for a work around, we decided to try changing the settings to that we print all events to the page (basically set the setting to 100 events per page). In doing that, even after cache clears, you can’t see any events beyond the first 10. If I click next (and am authenticated) I get a page that tells me there are no more events. When I go back, then I can see all of the events. If I click on an event to view it and then click the back button – I can one again only see 10 events.

This is somewhat similar to this person’s problem:

Control how many events show on List display.

We are not using the Divi Theme.

Is there an easier way to disable the next/previous buttons and just display everything? Any ideas on why all events don’t appear consistently when I want to display 100 per page?

Thanks much
Jessie

[Cliff]

Hi Jessie.

Thanks for the details.

Does your wp-config.php file force SSL Admin?

If not, I’d advise adding it and then trying again because the admin-ajax.php script will then load via HTTPS instead of HTTP (which is just a guess that this may be the issue).

If it’s still not working after forcing SSL Admin, please follow our Testing for Conflicts Guide and see if that helps narrow down the cause of this.

Let us know what you find out.

Thanks.

[Jessie]

We don’t allow any traffic to the admin-ajax. Is there any way to disable ajax for the plugin?

Thanks!
Jessie

[Cliff]

Hi Jessie. That would definitely affect things.

Our plugins use quite a lot of Ajax, and the WordPress Codex states that admin-ajax.php should be used even on the front-end.

What is your reasoning behind disabling access to admin-ajax.php and how are you blocking it?

[Jessie]

This reply is private.

[Cliff]

Thanks for your feedback. I can pretty safely say we won’t ever have an option to disable the Ajax functionality.

I can understand the protections around your login and admin areas, but the admin-ajax.php file is used in both front-end and back-end; it’s dual-purpose.

Therefore, I’d suggest you still protect what you want to protect but make the protection logic “smarter” to not disallow access to the admin-ajax.php file.

I’m guessing you already thought of this as an option, but I still thought I should share the idea, just in case. 🙂

[Support Droid]

This topic has not been active for quite some time and will now be closed.

If you still need assistance please simply open a new topic (linking to this one if necessary)
and one of the team will be only too happy to help.

[Author]

Posts