-
Notifications
You must be signed in to change notification settings - Fork 394
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
Shaarli opens link when asking to add link #216
Comments
Hi @basille this repository is currently unmaintained (see #191 (comment)). We have set up a community fork at https://github.com/shaarli/shaarli with many fixes. Can you try reproducing this problem using the fork, and report at https://github.com/shaarli/Shaarli/issues if it happens again? I suggest that you close this issue, it will likely not be fixed here and it helps cleaning up the bug tracker. Thanks |
Thanks, I have missed that! (I was actually wondering whether Shaarli was still maintained) No luck with the fork, though. I'll close this issue and open a new one in the fork page (with updated information). |
Well well well... :) I just had a flash, and disabled my Firefox extensions... Looks like one of these was causing the mess (I suspect RedirectCleaner). All is well in the end! I can use my Shaarli again (and I will update to the fork now that I know it exists!) Thanks for your very fast answer! |
Glad you sorted it out @basille |
I have the weirdest behaviour, which I could not track down...
For a couple of weeks now, if I click on "Add link" button, the usual pop-up opens, but instead of asking me the information I want to publish together with the link, it simply opens the link itself. As a result, I'm now completely unable to post any new link to my Shaarli.
Here is what I tried, among many combinations of these on several subdomains, to no avail so far:
Apache version is 2.2.26, PHP version is 5.4.25. I suspect a change on the web hosting I use, but I could not track it down either (most notably, I just switched to a new server, and the same problem is still there). Note that I don't recall making any change on Shaarli, or on our web account in general, just before the problem started. And Shaarli used to work beautifully for a long time before that...
Any hint?
Mathieu.
(note: I will be away starting from tomorrow, so please don't be offended if I don't answer before mid-January! I'll still check today)
The text was updated successfully, but these errors were encountered: