Joomla Templates Club 406,261 posts

[splico123 Friend splico123Join date: January 2007Posts: 339Downloads:80Uploads:7 Thanks: 24 Thanked: 93 times in 16 posts]

#167101

With fresh install of J1.7 and Teline IV there seems to be a problem when displaying blog. The published date is not showing. basically i think the com_content/blogitem is different from j1.6 so the blog date formating is lost and not overwriting in template.

actually just tested on multiple templates so it is the issue after upgrading to 1.7… com_content is differently formated

[Ninja Lead Moderator Ninja LeadJoin date: November 2014Posts: 16064Downloads:310Uploads:2864 Thanks: 341 Thanked: 3854 times in 3563 posts]

#404896

Yes Splico123,

That could be the reason. You can try checking the j1.7 template files of content for the changes and then correct the current j1.6 template. Or just wait a little more time, we are working in order to release the templates for j1.7 soon.

[splico123 Friend splico123Join date: January 2007Posts: 339Downloads:80Uploads:7 Thanks: 24 Thanked: 93 times in 16 posts]

#405447

It is the template com_content difference from the source joomla com_content

[TomC Moderator TomCJoin date: October 2014Posts: 14077Downloads:58Uploads:137 Thanks: 948 Thanked: 3155 times in 2495 posts]

#405485

splico123:

The reason for the issues with the “Blog” sections in a Teline IV based site (assuming you upgraded from the J1.5 version) is because the component powering the Blog section – i.e. K2 – is only compatible with J1.5x powered sites/templates.

This kind of issue is one of the most significant problems with regard to rushing to upgrade to J1.6 or J1.7 – which I touch on here –> The SMART & SENSIBLE Way To Upgrade

I, too, am working on a Teline IV based site project … but I am sticking with J1.5 for exactly the reason that the added functionality I want as part of the overall website dynamics and experience for my users can only be achieved, at this time, utilizing extensions that are not now (and no foreseeable roadplan for) compatible with J1.6 or J1.7.

Perhaps when J1.8 is eventually finalized and released – which is said to be a much more significant and long-lasting/supported release – that will be the time to facilitate a Joomla CMS system upgrade … depending on whether the “upgraded” options within J1.8 are actually worth the time/trouble of upgrading in the first place, that is.

😎

[splico123 Friend splico123Join date: January 2007Posts: 339Downloads:80Uploads:7 Thanks: 24 Thanked: 93 times in 16 posts]

#405712

<em>@tcraw1010 258795 wrote:</em><blockquote>splico123:

The reason for the issues with the “Blog” sections in a Teline IV based site (assuming you upgraded from the J1.5 version) is because the component powering the Blog section – i.e. K2 – is only compatible with J1.5x powered sites/templates.

This kind of issue is one of the most significant problems with regard to rushing to upgrade to J1.6 or J1.7 – which I touch on here –> The SMART & SENSIBLE Way To Upgrade

I, too, am working on a Teline IV based site project … but I am sticking with J1.5 for exactly the reason that the added functionality I want as part of the overall website dynamics and experience for my users can only be achieved, at this time, utilizing extensions that are not now (and no foreseeable roadplan for) compatible with J1.6 or J1.7.

Perhaps when J1.8 is eventually finalized and released – which is said to be a much more significant and long-lasting/supported release – that will be the time to facilitate a Joomla CMS system upgrade … depending on whether the “upgraded” options within J1.8 are actually worth the time/trouble of upgrading in the first place, that is.

:cool:</blockquote>

As that might be true in most circumstances it is well said. But the problem then is the fact that new installation is tighed to J1.7 and that said leaves a certain void in the template that needs to be addressed. Because it was working in J1.6 and now in 1.7 not is minor “bug” that can be fixed.
I am saying this because my client is not relying on K2 and without it that little part is supposed to work. At least thats my thought on the subject.

But all in all i have fixed it now since it was a minor change in the core and its all working as intended.

[TomC Moderator TomCJoin date: October 2014Posts: 14077Downloads:58Uploads:137 Thanks: 948 Thanked: 3155 times in 2495 posts]

#405715

<em>@splico123 259056 wrote:</em><blockquote>As that might be true in most circumstances it is well said. But the problem then is the fact that new installation is tighed to J1.7 and that said leaves a certain void in the template that needs to be addressed. Because it was working in J1.6 and now in 1.7 not is minor “bug” that can be fixed.
I am saying this because my client is not relying on K2 and without it that little part is supposed to work. At least thats my thought on the subject.

But all in all i have fixed it now since it was a minor change in the core and its all working as intended.</blockquote>

I am glad that you were able to resolve the issue – though I am a bit confused as to what you mentioned above.
Are you saying that your client does or does not want/rely the Blog feature via utilization of the K2 component?

Were you able to implement a different BLOG feature that is not tied/related to using the K2 component – or were you able to modify the K2 component code to work within the J1.7 structure?

On a related side note . . .
One of the issues/problems with feeling one “needs” or “must” upgrade to the newest Joomla version is exactly the issue/problem it seems you were facing – i.e. the fact that MOST of the extensions available for Joomla are not – and very likely will not – be updated for compatibility with either J1.6 or J1.7 (though I cannot make that statement with 100% certainty with regard to J1.7). The reason being is that the relative shelf-life for J1.7 is not going to be long at all . . . . as opposed to the forthcoming (in 2012) J1.8 – which will have a supported shelf-life of at least 18 months (according to the Joomla.org development team).

As such – and given the fact that, for all intents and purposes, J1.5x remains an amazingly strong and versatile Joomla platform – would it not make more sense to stick with a platform that provides for the MOST versatility for one’s clients in terms of compatible extension availability?

Simply some constructive food for thought – in the spirit of calm and respectful discussion.

🙂

[Author]

Posts