-
Notifications
You must be signed in to change notification settings - Fork 142
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
Permalinks of comments on lessons are broken in version 4.2.2.2. #541
Comments
Hi voria, Can you provide us link your site? We install LP v4.2.2.2 on site https://testlp.thimpress.com/courses. It runs normally. Thanks. |
Hello, I'm still working on my site and it's not online yet. Anyway, I just tried to post comments on https://testlp.thimpress.com and the same problem is happening there too. I've posted a couple of comments on lesson |
Hi voria, You don't see your comment, because, the system waits for approve like the image Thanks. |
Just for info, I've update to the just-released v4.2.2.3, the problem is still there. |
My comments at https://testlp.thimpress.com/ have been approved, and the problem is there as I described. I posted my comments at https://testlp.thimpress.com/courses/uncategorized/course-1/lessons/l1/. If you hover with your mouse over the comments' dates you can see the permalinks are wrong. |
Hi voria, We see it, we'll fix it soon. When we have done, we'll reply to you. Thanks for the feedback. |
As of title, comments' permalinks are non-working in version 4.2.2.2 and lead to a 404 error.
For example, suppose to have a course with the following permalink:
/courses/<course_name>
and a lesson assigned to it with enabled comments and the following permalink:
/courses/<course_name>/lessons/<lesson_name>
When an user posts a comment to the lesson, it gets a non-working permalink:
/lessons/<lesson_name>/#comment-<number>
instead of the correct one:
/courses/<course_name>/lessons/<lesson_name>/#comment-<number>
Downgrading the plugin to version 4.2.1.1 fixes the error.
The text was updated successfully, but these errors were encountered: