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
Call to undefined function yourls_nonce_url() #2661
Comments
Oh, indeed. I moved some functions from one file to another without thinking about guys running a public shortener. Quick fix until next release: simply add |
I've added it, but got |
|
I‘ve added But this produces these error messages (
|
Owww yeah my bad, you're right. You need to include the full path at this point, of course. I'm editing the first comment. |
This works in config.php: require_once( dirname( __DIR__ ).'/includes/functions-auth.php'); Won't this bug wipe out everyone and not just me? Seems like something that should have been fixed ASAP??? Or maybe very few have updated to 1.7.9? |
This didn't justify, to me, another release the next day just to fix this. |
Mr. OZH: Thank you for your kind attention and for all you do with this system. It is not fixed in Master. I downloaded the zip 1.7.9 from https://github.com/YOURLS/YOURLS/releases and the problem happened until I put in the line of of code in config.php. I understand what you say about access but I don't need to have it private. What I'm saying is that if you have the config set to: define( 'YOURLS_PRIVATE', false ); AND you don't have the "require_once" line in config.php the issue occurs in 1.7.9. Try it! |
It's fixed in master, ie the current development code. You've just reinstall the same 1.7.9 that you had already installed. If you want to fix this without adding the line to your config, download https://github.com/YOURLS/YOURLS/archive/master.zip, which is the 1.7.9 you already have + the commits that have happened since 1.7.9 was released, and in particular the one that fixes the aforementioned problem (fd4b927) |
I did not know about the "master' . At the top of the admin screen was a notice saying that 1.7.9 was the latest version and the link took me to https://github.com/YOURLS/YOURLS/releases/tag/1.7.9 and I got the zip from there. Anyway, 1.7.9 is working fine with the 'require" line in config.php. I also took your advice and made the system 'private' since that is what most people do. Works fine. Thus, I won't update again and will wait for 1.7.10 or whatever comes next. Thanks for all your help on this. I wish I had known about YOURLS a long time ago. It works great and is easy to use. |
1.7.9 is the latest "release", and "master" refers to the on-going development. Once in a while, we "release" what is on "master" (with a newer version number: 1.7.9, 1.7.10, or 1.8 if we introduce new features, etc...). |
But since the Admin screen points the user to the 1.7.9 screen and not Master, people (like me) are going to download the 'broken' code. I guess what I was looking for was the 'stable' or 'production' version and I assumed that 1.7.9 was it since that is where I was directed to get the upgrade. |
It is. Cutting a new release for every bug fix would be pretty annoying for us and for YOURLS admins who'd keep seeing that a new version is available multiple times a month. So we generally don't release a new version until we collect enough fixes to make it worth doing. This issue affects a small percentage of installs and has a simple workaround, so it's really not worth pushing a new version just for that. |
I agree that the workaround was simple, but finding it was difficult. Maybe it is posted somewhere besides here and I just didn't find it? I spent quite a bit of time on Google looking for the error message with respect to YOURLS. I thought it might be in the WIKI or on the blog or maybe on the homepage. I doubt that the average usr would have found it... but perhaps YOURLS is not used by 'average' people and only those with advanced tech knowledge... FTP, code editing skills, etc. |
Pinned to aid visibility. |
Since update to
1.7.9
I get this error:api.php looks like this:
The text was updated successfully, but these errors were encountered: