-
-
Notifications
You must be signed in to change notification settings - Fork 193
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
v.4 to v.5.1.4 update #166
base: master
Are you sure you want to change the base?
Conversation
@shenyman can you please check phpcs for the PermissionsController? |
Apologies! Won't PR without phpcs checks anymore! |
I am sure there is a way to PR my fork, but don't do it since you did a lot of work on this one already. Let's get this done with tests passing and then we can see stuff that we might want to change from the other PR etc. |
tag.a does not resolve the correct url as link_to added url
@niden, in your PR #165, you have a commit af30873 where most of the enhancements are related to removing link_to and adding a tag.a (TagFactory). Because I'm installing Vokuro in a subfolder, I noticed that the main links became 'localhost/vokuro/users/users' after an action. Is this because tag.a does not resolve, and should not resolve by design, the correct URL as link_to does? I've added 'url' resolver to layouts/private.volt only and committed. Not sure if this is the correct way. |
@niden can we try the tests one more time? |
edited ext-phalcon to ^5.0.0
There is only master branch and no v.4 branch, as mentioned in the readme NOTE. You may create one or merge and update the vokuro.