-
Notifications
You must be signed in to change notification settings - Fork 20
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Paged NextGen Galleries Broken with Custom Permalinks 1.62 #38
Comments
@McYolic Do you have any dev or staging server where you can update the plugin the plugin and provide the URL of it with Site access? It will save my time to generate this issue. |
It's happening across multiple builds but here's a clean test install (Wordpress's default 2020 Theme) with everything fully updated - http://dev.shiskey.com/critter-gallery You'll see NexGens pagination along the bottom no longer works unless Custom Permalinks is rolled back. |
@McYolic Thank you for providing the test install access with FTP. I have updated your comment and removed the access details from it for the security purpose. |
@McYolic Thank you for your help and providing your website access. You can find couple of PHP errors in your test install log because of me so please ignore them. I have fixed this issue and will release it tonight or tomorrow in |
@McYolic I have released alpha version before the official release of the You can download the alpha version from here: |
Seems to have done the trick. Updated to 1.6.3 alpha on several live professional builds as well as the dev link without issue - Thank you for continued support of this excellent plugin. |
@McYolic Thank you for providing your feedback 😄 If you like the plugin then please provide your valuable feedback to the WordPress Forum. and save this repo in your Starred Repos list. |
Paged NextGen Galleries seem broken with Custom Permalinks 1.62. Rolled back to Custom Permalinks Version 1.5.1 and that "fixed" the issue for now but would like to update the plugin without breaking galleries.
The text was updated successfully, but these errors were encountered: