-
Notifications
You must be signed in to change notification settings - Fork 0
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
Possible solution to ! trigger not enabling the popup #6
Comments
In my case there seems to be a conflict with Advanced Slides Plugin. I could fix this with the following steps
|
I just tested this on a fresh install and had the exact same issue as you describe. At least I can finally reproduce the issue! Seems that the problem is with the autosuggest feature from advanced slides. By default, their suggest modal is active, and it doesn't have any trigger characters. It just triggers constantly on every input all the time. So I suppose any other suggest modals loaded after it are getting clobbered. Natural Language Dates doesn't even work under those same conditions. @ksdavidc do you use Advanced Slides? |
yes both advanced slides (which has since been forked to Slides Extended and Natural language dates. A bit busy right now or I would try to do some triage, but you are on the right track. You should probably check if the problem persists in the new version of the Slides, but it seems to be working for me as I have it now. |
At this point I'm confident the issue is caused by advanced-slides (and slides-extended). |
Was getting the same issue as given here: #3 (comment)
where hte >! trigger was not triggering the popup.
I was checking for a possible plugin conflict, since the sandbox with just callout manager and suggester seemed to work.
I used divide and conquer plugin, and repeatedly went down a level until eventually the trigger worked. Then I worked my way back up all the way and this seems to have fixed it. Not sure why it fixed it, since I have all the same plugins installed, but now it works, even after restart.
The text was updated successfully, but these errors were encountered: