Please upgrade here. These earlier versions are no longer being updated and have security issues.
HackerOne users: Testing against this community violates our program's Terms of Service and will result in your bounty being denied.
Vanilla version 2.3 YAGA 1.1 setting page not found
super_rookie
New
My vanilla version 2.3 then i install YAGA 1.1 can't setting picture below :
Please help me thank you
0
Comments
this log message :
192.168.2.2 - - [17/Feb/2017:20:25:28 +0700] "GET /vanilla/yaga/settings HTTP/1.1" 404 9577 "http://192.168.2.8/vanilla/dashboard/settings/applications" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/56.0.2924.87 Safari/537.36"
I test in version 2.2 again
I install yaga-application 1.1 and enable this app
after that i login to my page but error
It seem not work for me.
Please tell me for fix this problem
Thank you
192.168.1.10 - - [18/Feb/2017:23:43:02 +0700] "GET /vanilla/ HTTP/1.1" 256 709 "-" "Mozilla/5.0 (Windows NT 10.0; WOW64; rv:51.0) Gecko/20100101 Firefox/51.0"
This might help
https://open.vanillaforums.com/discussion/25111/about-error-404-not-found
You need to set up pretty urls for this app to work
❌ ✊ ♥. ¸. ••. ¸♥¸. ••. ¸♥ ✊ ❌
I also encountered this issue under 2.2 and 2.3 with Yaga 1.1.
@hgtonight: Did you encounter this before?
Do you have Pretty URL enabled ? This works perfect for me on 6 different Vanilla installations.
❌ ✊ ♥. ¸. ••. ¸♥¸. ••. ¸♥ ✊ ❌
@vrijvlinder: Yes, i read what you mentioned above. It's enabled.
When you updated YAGA , did you first disable it and delete the app ? Because he changed the place for some files in the most recent, and if you still have the old files in the old place, this might be the problem.
❌ ✊ ♥. ¸. ••. ¸♥¸. ••. ¸♥ ✊ ❌
This is my working version, maybe you can compare the two and find what is wrong with yours.
❌ ✊ ♥. ¸. ••. ¸♥¸. ••. ¸♥ ✊ ❌
Exactly that was the case, i made a total clean install of yaga. Now it work flawless. Thank you!
There is still some issues, like the "Best" page can not be called and leads to a 404 and others. But i'm investigating.
You might need to empty the .ini files from the cache... my Best of works fine.
❌ ✊ ♥. ¸. ••. ¸♥¸. ••. ¸♥ ✊ ❌