Skip to content
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

Slider Links will not open. #11

Closed
cherrykoda opened this issue May 19, 2021 · 6 comments
Closed

Slider Links will not open. #11

cherrykoda opened this issue May 19, 2021 · 6 comments
Assignees
Labels

Comments

@cherrykoda
Copy link

Clicking on any slider, with default slider settings across the board, will not open the link attached to the slide.

The only console output is a warning (attached):
image

@cherrykoda
Copy link
Author

We've stripped out EVERY piece of JS and CSS from the site leaving only the slider's assets that are loaded with the plugin. The links don't work.

As soon as jQuery was removed, preventing any jQuery from functioning, the links worked. We believe this indicates an issue in the plugin's JS. Possibly a prevent default gone rogue on clicks.

Our client paid for the plugin and is not happy.

@cherrykoda
Copy link
Author

Chrome Latest Release, Windows 10

@andrelopez andrelopez self-assigned this May 20, 2021
@andrelopez andrelopez added the bug label May 20, 2021
andrelopez added a commit that referenced this issue May 20, 2021
andrelopez added a commit that referenced this issue May 20, 2021
@andrelopez
Copy link
Member

@cherrykoda We just released Enupal Slider v1.4.0 with a fix to this issue. Please update the plugin and let us know how it goes.

@cherrykoda
Copy link
Author

cherrykoda commented May 20, 2021

@andrelopez on a fresh install with version 1.4

Yes, the links are clickable. But before we get to that point:

  • Double Clicking the Slide to edit its information generates a server error. We were able to fix this by editing the slide's redactor config as per this logged issue: Unknown error editing assets #8 (The fix someone posted there works, but needs to be implemented into your codebase)

image

  • Asset Volumes. When installed the default file system path is wrong, and has to be edited manually. It should be based on Craft 3's @webroot relative paths instead of system pathing. @webroot/assets or @webroot/uploads or @webroot/public etc...

  • Renaming the Slider breaks the slider - gets this error on save. Reloading the page returns user to the listing screen.

image

  • Renaming the slider causes the assets to disappear for that slider, the slider does not create new folder OR move the existing folder/rename existing folder.

image

The most critical issue:

On deployments, Craft's Project config implements the fields, plugin data, etc. but then the plugin install does the same causing duplicate fields, field handles, asset volumes, etc. When removing the duplicates, the database breaks and the entire site goes down. The only way to resolve has been to 'restore project config' from database. The only way to avoid it is to have the craft site set to not utilize the project config feature. This is site breaking, and not fixable or workaroundable on our end.

Really sorry to tack all of this on the linking issue - but its received no attention on the other issue logs and I have your attention here. Without that project config issue fixed at a minimum this plugin is unusable.

@andrelopez
Copy link
Member

@cherrykoda thanks for reporting. Let's keep track of these errors on the following tickets:

@cherrykoda
Copy link
Author

Great, thank you!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants