When I write a new comment to a CGBlog article using CGFeedback, I get the wrong origurl (the one from another CGBlog-article).
The error already occurs with the first saving of the comment in the DB.
The orig_url saved in the DB stays the same as long as I am using the same browser-window (session?) and is the first Blog-URL, I visited in this session.
But this is not correct (unless I have a missconcept here) - the origurl is for exemple used to guide the user back to the original article - of course he might give more comments to different articles.
Any Idea?
All Modules and CMSMS up to date!
User-Notification {$orig_url} in CGFeedback not correct
Re: User-Notification {$orig_url} in CGFeedback not correct
- + - + - + - + - + - + -
LATEST TUTORIAL AT CMS CAN BE SIMPLE:
Migrating Company Directory module to LISE
Migrating Company Directory module to LISE
- + - + - + - + - + - + -
Re: User-Notification {$orig_url} in CGFeedback not correct
Hi Rolf,
Thx for your reply.
No, I don't think so.
The url is getting saved wrong with the first INSERT of a comment into the DB.
As far as I understand, the user-notification would be called later in the admin and veryfication-process.
But I'll test it and change it according to your bug-entry!
The Bug you filed is the only place, with this inconsitency orig_url vs. origurl.
Through the rest of the php-files the variable is called origurl.
So, I tested it...no, no change, the origurl is kept the same during one session despite giving a comment to another blog-article.
Funny, I noted that when I give another comment to the same Article, there will not be saved another comment in the DB, but instead gets a modified entry in the extra-field of the comment-table.
( I don't use FEU, so there should be no modifying possible)
In the documentation is mentionned a session params, but then not shown or explained:
I cannot understand this like that.
Thx for your reply.
No, I don't think so.
The url is getting saved wrong with the first INSERT of a comment into the DB.
As far as I understand, the user-notification would be called later in the admin and veryfication-process.
But I'll test it and change it according to your bug-entry!
The Bug you filed is the only place, with this inconsitency orig_url vs. origurl.
Through the rest of the php-files the variable is called origurl.
So, I tested it...no, no change, the origurl is kept the same during one session despite giving a comment to another blog-article.
Funny, I noted that when I give another comment to the same Article, there will not be saved another comment in the DB, but instead gets a modified entry in the extra-field of the comment-table.
( I don't use FEU, so there should be no modifying possible)
In the documentation is mentionned a session params, but then not shown or explained:
and below:only when policy (see below) is "normal".
and thats all., when session is set to "policy"
I cannot understand this like that.
Re: User-Notification {$orig_url} in CGFeedback not correct
Ok, the previous mentioned "modify"-entry has resolved by the setting in CGBlog to not allow FEUs to manage their entry.
(this should be noted in the documentation, that FEU-settings apply to CGFeedback too)
But the origurl persits. I still get the wrong origurl when I make an other comment to another blog article.
(this should be noted in the documentation, that FEU-settings apply to CGFeedback too)
But the origurl persits. I still get the wrong origurl when I make an other comment to another blog article.
Re: User-Notification {$orig_url} in CGFeedback not correct
For right now, I solved it like this:
I save the orignal url in CGFeedbacks Key3. Like:
$Key3 is accessible in the User-notify E-mail template.
This way, I can redirect with certainty the user to the article, he subscribed to.
I save the orignal url in CGFeedbacks Key3. Like:
Code: Select all
{CGFeedback key1="Blog" key2=$entry->id key3="{module_action_link module=CGBlog action=detail articleid=$entry->id urlonly=1}"}
This way, I can redirect with certainty the user to the article, he subscribed to.