Wrong url on tag list page

Hi,

Can you please clarify? I visited the link you provided and the links of the images are the same to those in the titles.

Regards

Are you sure that you have the latest version of Econa? In the new version the link is generated on line 264. The code was on line 254 before the fix. In any case, I will check it again and let you know. Thank you for reporting this.

Regards

Not sure what you expect to get fixed. In the latest version line 254 is a blank line. The issue has been fixed a long time ago. The code now is the following and it works fine in all the tests I have made:

		// Link
		$image->link = '';
		$image->modal = '';

		if ($field->fieldparams->get('link'))
		{
			if ($context == 'com_content.article')
			{
				if ($view == 'tag')
				{
					$image->link = JRoute::_(ContentHelperRoute::getArticleRoute($item->core_content_id . ':' . $item->core_alias, $item->core_catid, $item->core_language));
				}
				else
				{
					if (isset($item->slug))
					{
						$slug = $item->slug;
					}
					elseif (isset($item->alias) && $item->alias)
					{
						$slug = $item->alias . ':' . $item->id;
					}
					else
					{
						$slug = $item->id;
					}
					$image->link = JRoute::_(ContentHelperRoute::getArticleRoute($slug, $item->catid, $item->language));
				}
			}
		}

No, you are wrong. When you are in a tag view the item->core_id is the article ID. It works fine for me in all my tests. Have you tested this code? What's your Joomla version?

Regards

If you are using the latest version and the issue remains then something else is going on. In that case please create a new private ticket and provide administrator credentials and FTP access so I can troubleshoot this.

Regards

The variable is core_content_id this was just a typo in my comment. In any case the provided code should work. If not please create a private ticket and provide the information I requested so I can troubleshoot this.

Regards

Again:
Just tested clean Joomla 3.9.16 and latest Econa 1.7.5 and everything works fine for me.
And again:
If it is still not working for you create a private ticket and provide the information I requested so I can help you.

Regards

The issue has been fixed on 16th of April 2019. A few days after you reported. The fix was included in the version 1.7.4 which was released on July 2019. You can see for yourself in the release notes:

https://www.firecoders.com/releases/econa/econa-1-7-4


So the issue is considered solved as of July 2019.
Again, this works fine in all my tests. I cannot fix something I cannot reproduce. If you provide the details I requested I will troubleshoot this. Otherwise there is nothing more I can do. I hope this makes sense.

Regards

We are not releasing a new version every time an issue is fixed. Unless it's a critical one. If a user requests a fix for an issue we always provide the code changes so he doesn't need to wait for the update.

In any case, the issue has been fixed, there are no other reports and we cannot reproduce the issue in any test.
Since you don't provide access to your site facing the issue, there is nothing more I can do. If you change your mind please let me know.

Regards

I will not apologize for something that happened only in your mind. Here are the facts so people reading this can understand who is lying:

1. You opened this issue on 15th of April 2019.
2. The issue was fixed in the codebase the next day. On 16th of April 2019.
3. On 16th of May you requested to send you an update because your subscription was expiring. I gave you the fix even if I shouldn't. We are not enforced to release an update every time a client's subscription ends.
4. The fix was included in the version 1.7.4 which was released on July 2019.
5. You renewed your subscription on 29th of February 2020. I never forced you or anyone to buy a subscription. Recall now or prove it.
6. The same day you created this ticket. Since then, I am trying to provide help and and you just don't accept it.

Just checked our records and you have created six other tickets and all of them are resolved. And now you claim that the support is disappointing!

After six resolved tickets and the fact that I gave you the fix even if I shouldn't you should be thankful. Coming here after all this and requesting an apology makes you unthankful and arrogant.

For the last time before I close this ticket, I am asking you to provide access to your site so I can help you.

Obviously you have nothing to say about the facts I wrote, that's why you are trying to offend me. It's really fine. I will not get into this.

Regarding the rest of your response, there is no partially true. It's either true or not. The things I listed are facts there is no room for doubt. And they can be proved.

Regarding the ticket you refer to, your subscription had expired. I gave you the fix (while I shouldn't) which is working for me and the rest clients. And then you come back responding that the fix is not working for you. So you asked for support while your subscription was expired. That's why this ticket remained unresolved.

In any case, since you do not want to get help I am closing this ticket. The issue is considered resolved since it works in all the tests I have made and we have no other reports from other clients. If you change your mind and you want to get help create a new one.