By Tom Flemming Sigsgaard on Tuesday, 01 March 2016
Posted in Technical Issues
Likes 0
Views 338
Votes 0
Hi
After I activated the EasyBlog composer, the linking for the old blogs (the one that are created with Tiny Mirror) seems to loose the linking.
The linking (url) after the domain name is ok - but the domain name is dropped.
It also seems like it only applys to the blogs that appear in the menu link "BLOG FRONTPAGE"
I am not really shure how to explain this issue, so I have enclosed a image to illustrate the issue.

The problem started when I switched from Tiny Mirror to the build in EasyBlog composer in the admin area.
Hi Tom,

It seems like you have made some changes with the href link inside your /components/com_easyblog/themes/wireframe/nickel/blogs/latest/default.main.php at line 123 where it add an extra slash ( / ) before the url hence causing the issue.

I've fixed this by removing the extra slash and everything is working correctly now. Please have a look.
·
Tuesday, 01 March 2016 18:19
·
0 Likes
·
0 Votes
·
0 Comments
·
Hi Ezrul
Thanks for reply, and help
I did not change any scripts, - I only activated the EasyBlog Buld in composer from the Administrator page.

Thanks
Tom
·
Tuesday, 01 March 2016 21:51
·
0 Likes
·
0 Votes
·
0 Comments
·
Hi again -
I have noticed that something really strange happened after you fixed this issue for meg.
Take a look at the screen dumps I have enclosed..

Thanks
Tom
·
Tuesday, 01 March 2016 22:18
·
0 Likes
·
0 Votes
·
0 Comments
·
Hi Tom,

I've check your frontend site it seems fine, it may be your page cache.
see my snapshot: http://screencast.com/t/GJWd3Pwhz4B
·
Tuesday, 01 March 2016 23:36
·
0 Likes
·
0 Votes
·
0 Comments
·
Hi
thanks for reply.
No it´s not the cache.
In the homepage - everything loosk great - but in all the subpages you can see the problem + in the admin section there is al lot of issues (like the one I send you above - screendump)
thanks
Tom
·
Wednesday, 02 March 2016 00:06
·
0 Likes
·
0 Votes
·
0 Comments
·
Hey Tom,

I am sorry for the delay of this reply,

It seems like those error is coming from Joomla and GTranslate module, I already help you turn off the error reporting from maximum to default, these error will not show up now.

Can you give it a check now?
·
Wednesday, 02 March 2016 12:00
·
0 Likes
·
0 Votes
·
0 Comments
·
Hi Arlex
Thanks for reply
Yes - this removed the error - thanks.
Now I know that it is GT Translate that is creating this error
Thanks again
Tom
·
Wednesday, 02 March 2016 13:09
·
0 Likes
·
0 Votes
·
0 Comments
·
You're welcome, glad to heard your issue resolved.
·
Wednesday, 02 March 2016 13:23
·
0 Likes
·
0 Votes
·
0 Comments
·
View Full Post