Discuss Joomla! 1.7.0 Released

[pe7er]

Here you can discuss about the release of Joomla! 1.7.0.

See Announcement: http://forum.joomla.org/viewtopic.php?f=8&t=637125

[oldtott]

Hi, just updated my site and everything has disappeared apart from the background image of my Artisteer Template!!!
The files are still in the admin end but no show on the internet.

[infograf768]

I just upgraded to 1.7, and it went very easy. Only problem is dat I now have a website without a loaded template. And when I select a template (beez20 for example), the website stays "Blank"...

underneath I get this error:
Fatal error: Call to a member function getPath() on a non-object in /home/w0824589/domains/raymondsmits.com/public_html/joomla_new/libraries/joomla/application/categories.php on line 516


See here what I mean:
http://www.raymondsmits.com/joomla_new

How can I fix this???

EDIT
Also when I go to "Global Configurations, Site" The select buttons of the options "site, system,server,premission" don't work. I then get a error underneath in IE9:

Foutdetails webpagina

Gebruikersagent: Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 5.1; Trident/4.0; .NET CLR 2.0.50727; .NET CLR 3.0.04506.30; .NET CLR 3.0.4506.2152; .NET CLR 3.5.30729)
Tijdstempel: Tue, 19 Jul 2011 14:51:38 UTC


Bericht: Kan de eigenschap type niet opvragen. Ongeldig argument.
Regel: 6
Teken: 30
Code: 0
URI: http://www.raymondsmits.com/joomla_new/ ... alidate.js


Bericht: Deze eigenschap of methode wordt niet ondersteund door dit object
Regel: 473
Teken: 25
Code: 0
URI: http://www.raymondsmits.com/joomla_new/ ... ls-core.js

Test with another browser first.

[oldtott]

Sorry no - I used Google Chrome and the same thing is happening.

[Raikkonen_WC]

For me Also. Tested it with Chrome and Firefox. Same error on the main page.

[alikon]

even i think we are a bit off-topic
wich template are you using ?

[Chimo]

Artisteer released an new version today to fix the template problem. You will have to open up your .artx file and exported again. That will clear up your template problem. Latest release for Artisteer is: Artisteer 3.0.0.41778 for Windows.

[Raikkonen_WC]

even i think we are a bit off-topic
wich template are you using ?

I use Beez20, the standard Template. He does it with every template I chose

[Beat]

Congrats to Joomla team and community for this first Joomla 1.7 stable release.

Just to avoid surprises: We highly recommend checking compatibility of your installed extensions before upgrading Joomla 1.6 to 1.7 !

Just one example of the Community Builder extension:

Existing Community Builder 1.4 (running on Joomla 1.0, 1.5 and 1.6) is NOT compatible with Joomla 1.7.

We have been working hard last weeks in order to adapt Community Builder 1.4 to Joomla 1.7 and now that Joomla 1.7 is released, we have already released a corresponding Community Builcer 1.7 RC release within hours of the release of Joomla 1.7.0. (this RC release is, as any other CB RC release, available as usual to all our professional members first, before being released stable to everybody).

Community Builder 1.7 (non-RC) will be released and made available as usually as a free download to everybody, on August 1st, after we make sure with the RC version and get the feedbacks that it runs well on all Joomla versions.

More information about our release cycle for Community Builder on www.joomlapolis.com

[infograf768]

To all.

Before posting about issues upgrading, BACK-UP and test locally.
Then, make sure

1. You attempted the upgrade on a 1.6.5 Joomla version

2. You have followed the upgrade instructions posted here:
http://docs.joomla.org/Upgrading_1.6.5_to_1.7

3. You have tested by a local upgrade that all your extensions are compatible.

4. If you are using other languages than English (en-GB), that you have updated your lang packs:
http://joomlacode.org/gf/project/jtranslation1_6/frs/

Note: Thanks Beat for the info.
This also concerns extensions like Gantry, Kunena, Artisteer, Yootheme, Joomsocial, EasyBlog, JoomlArt T3

[sophithequeen]

Fire fox 5 is not working which version is should use.

[Pmavrovic]

I have a question regarding long term releases.
I am currently using 1.5.23 on my production site. I am aware that 1.5.x has been a long term release and I don't want to have to get stuck totally re-working my site from scratch every 6 months.
Can anyone tell me when the next long term release come out and if there may be an upgrade path from a previous long term release?

Kind regards,

[Nick Savov]

Hi and welcome to the Joomla forum, Pmavrovic!

First you don't have to rework your site from scratch every six months because we have 1 click upgrades now and 99%+ of extensions and templates will work in 1.7 as they did in 1.6 (this is my opinion and theoretical considering the API changes...either way make a backup and test in a test environment first just to be safe). 1.7 is a direct upgrade of 1.6.

The next long term release will be in January and it will be called either 1.8 or 2.0 (though I'm hoping it's 2.0). And yes, there will be an upgrade path from 1.5 (assuming all goes well).

Kind regards,
Nick

[infograf768]

The next long term release will be in January and it will be called either 1.6 or 2.0 (though I'm hoping it's 2.0).

1.8 or 2.0

[designtu]

Soon as I upgraded I can no longer edit my menu's. Opens all option at once and gives an error on the bottom

Fatal error: Cannot instantiate abstract class JDatabaseQuery in /home/interact/public_html/modules/mod_roknavmenu/fields/modules.php on line 38

Please help.

[alikon]

try disabling the mod_roknavmenu maybe is not 1.7 ready

[Nick Savov]

1.8 or 2.0

Good catch! Silly typos

[HThole]

we have 1 click upgrades now and 99%+ of extensions and templates will work in 1.7 as they did in 1.6. 1.7 is a direct upgrade of 1.6.

Sorry, this is definitely NOT true.

Update from J 1.6.5 to 1.7.0 just killed my Site. Most extensions do NOT work, only a few. (Note: I had a backup - thank god for Akeeba!)

And worst: Why the hell is 1.7.0 a security update, when it's so buggy at the very end (this means extensions are no more working!)? There has to be a version 1.6.6, because you have to wait days and weeks for all needed extension updates!!!

To me it seems the Joomla-team isn't still in track with the new strategy. Joomla-Users outside are NOT Guinea-pigs like mice in science to make tests with.

This is NO critique to Nick, but to the Joomla-team. I think most users need to have working extensions. It is crappy to kill your site with an update of the core-system, by killing the functionality of the site! Even Community-Builder doesn't work on 1.7.0 by now, and CB ist not nothing.

It is definitely NO solution to encapsule a security-update in a .0-major-version - please make your job in the sense of the user and publish a V 1.6.6. If this is not needed due to a only medium security-threat, 1.7.0 should not be named as security-update.

Joomla is at high risk to loose relevant parts of his users when this bumpy course will not stopped.

H

[Nick Savov]

Hi and welcome to the Joomla forum, HThole!

I'm sorry but the fact that it didn't work for you does not mean that my statement is definitely not true. You could be the < 1% with an issue. Your saying that most extensions don't work is simply wrong. Most do work. API between version practically wasn't changed so "most" extensions would work.

Perhaps you could start by what errors you are getting? I'm more than willing to help out

Kind regards,
Nick

[urednik]

Nick,
if you think only 1% people use CB and Kunena,
than you are totally irrelevant. Sorry to say that.

And yes, I am also a little disappointed, by kinda expected it so I did not update, although my only extension is Kunena.

[nant]

First you don't have to rework your site from scratch every six months because we have 1 click upgrades now and 99%+ of extensions and templates will work in 1.7 as they did in 1.6. 1.7 is a direct upgrade of 1.6.

Is this an official Joomla statement?

If not, please state that it is your opinion and to make it even more strong perhaps indicate how you reached this conclusion.

People reading such statements will rush to take a quick single-click upgrade thinking that 1% is a good risk factor.

In fact most of the major Joomla 1.6 compatible extensions have issues with Joomla 1.7 as posted earlier in this thread.

Community Builder team is working on release 1.7 to address this issue as soon as possible (RC currently in internal testing and Professional membership testing).

I think the fact that this 1.7 release was deemed a security release - really why not go with 1.6.6 instead (?) - has caused people to rush to upgrade.

Back on track - no matter what people say, it's up to the website administrators to have sandbox environments and test each upgrade, new extension install, etc - BEFORE going productive.

No one will do this for you - period.

[alikon]

it's up to the website administrators to have sandbox environments and test each upgrade, new extension install, etc - BEFORE going productive.

holy words
it seems there are a lot of "sunday website administrators"

[darb]

People reading such statements will rush to take a quick single-click upgrade thinking that 1% is a good risk factor.

In fact most of the major Joomla 1.6 compatible extensions have issues with Joomla 1.7 as posted earlier in this thread.

Yes I think you are very right about this.

To make update tests with a fresh J 1.6.5 install as core devs doing is something different compared to have a live J 1.6.5 with many extensions and make a oneclickupgrade.

I am very sure that many of those sites doing this will have problems. Joomla core is ready but not the 3pds yet.

So make test upgrades first before going live with the real J 1.7.0 update is my advice bcs of 3pds compatibility issues..

If your J 1.7.0 update fail you can use AdminTool to make a revert back to J 1.6.5 with one magic click

[HThole]

Perhaps you could start by what errors you are getting? I'm more than willing to help out

Thanks at first, Nick.

The very problem ist one which beat from CB stil adressed: The part of security update in J 1.7.0 should have been J 1.6.6 instead. It is unhealthy to stop J 1.6.5 and bring out 1.7.0 instead from this aspect.

As beat wrote also, CB Team seems to have no appropriate time to prepare CB for J 1.7.0. When you are running such a component, this is a major failure if it isn't working.

The failure which appeared on my system was the following:

Crash Update J 1.7.0.JPG

This will occur to all CB users, i think.

In my opinion Joomla lost one point - the frist new-cycle-release simply failed.

[Nick Savov]

Nick,
if you think only 1% people use CB and Kunena,
than you are totally irrelevant. Sorry to say that.

And yes, I am also a little disappointed, by kinda expected it so I did not update, although my only extension is Kunena.

Read my statement please. I didn't say 99% of people, I said 99% of templates and extensions.

[Nick Savov]

First you don't have to rework your site from scratch every six months because we have 1 click upgrades now and 99%+ of extensions and templates will work in 1.7 as they did in 1.6. 1.7 is a direct upgrade of 1.6.

Is this an official Joomla statement?

No it's not.

If not, please state that it is your opinion and to make it even more strong perhaps indicate how you reached this conclusion.

Done.

People reading such statements will rush to take a quick single-click upgrade thinking that 1% is a good risk factor.

They should make a backup and test it on a test server either way. That was already mentioned earlier in the thread...I've added that comment to my original statement for clarification though.

In fact most of the major Joomla 1.6 compatible extensions have issues with Joomla 1.7 as posted earlier in this thread.

I see a mention of CB, Gantry, Kunena, Artisteer, Yootheme, Joomsocial, EasyBlog, JoomlArt T3. Sorry but this does not compromise most or even close to most of the major Joomla 1.6 compatible extensions nor is it greater than 1% of the total. Second if you're running the latest version of Gantry (released before 1.7) there should be no issues (that I am aware of and that I've seen) so I don't know why that's listed. Same goes for Jomsocial (as far as I know...check their forums and you'll see what I mean).

T3 the only thing I am are of is concerning this issue which was posted Jun 2nd and so should have been corrected:
https://groups.google.com/group/joomla- ... 47a.?pli=1

The rest I don't know about and won't be looking into in the near future unless I see someone actually report the issue.

Once again, my quote still stands. People don't have to majorly redo their sites every 6 months. It's direct upgrades from here.

Back on track - no matter what people say, it's up to the website administrators to have sandbox environments and test each upgrade, new extension install, etc - BEFORE going productive.

No one will do this for you - period.

Very true, very true! The same can be applied to developers. Developers need to do a better job (IMO) of testing beforehand:
http://docs.joomla.org/Potential_backwa ... tform_11.1
https://groups.google.com/group/joomla- ... 47a.?pli=1

This is not directed at you and the CB Team, but rather just a general statement. A lot (not all) of these things can be easily avoided by developers.

Kind regards,
Nick

[Nick Savov]

p.s. So that you guys would quit bothering me about my 99% quote

How many of Joomla's 2200 1.6 native extensions are reported as causing issues in the "Migrating and Upgrading to Joomla! 1.7 / Joomla! 1.6" forum?
http://forum.joomla.org/viewforum.php?f=625

Just because something happens to you does not put you in the majority and it does not mean that Joomla's developers are incompetent. Perhaps it would be better to ask why a security release was issued in 1.7.0 rather than using 1.6.6.

[Nick Savov]

Perhaps you could start by what errors you are getting? I'm more than willing to help out

Thanks at first, Nick.

You're welcome, but I may not be of much help I finally had time to look into the errors but please let me first respond to your other statements.

The very problem ist one which beat from CB stil adressed: The part of security update in J 1.7.0 should have been J 1.6.6 instead. It is unhealthy to stop J 1.6.5 and bring out 1.7.0 instead from this aspect.

What I've learned is that Joomla's core developers are smart and definitely know what they are doing. That's not to say that they don't make mistakes, they definitely do. However in situations like these it's usually best to first ask why something was done rather than immediately conclude that they were wrong.

As beat wrote also, CB Team seems to have no appropriate time to prepare CB for J 1.7.0. When you are running such a component, this is a major failure if it isn't working.

http://www.joomla.org/announcements/rel ... eased.html
http://www.joomla.org/announcements/rel ... eased.html
http://www.joomla.org/announcements/rel ... eased.html
http://www.joomla.org/announcements/rel ... eased.html

I don't know the CB Team's schedule and time constraints, however I think a month and a half was appropriate, don't you? I'm not at all blaming the CB Team or saying that didn't do things well or saying that they failed anyone. I'm willing to assume the best on their end and assume that there was good reasons why they weren't ready. However what I am saying is that a month and a half is appropriate, reasonable, and fair, especially considering the lack of API changes.

The failure which appeared on my system was the following:

Crash Update J 1.7.0.JPG

This will occur to all CB users, i think.

I couldn't replicate this on a clean install of 1.6.5 and the latest version of CB. Are you sure you used the latest version of CB?

Here's the error I got:

Code: Select all

Fatal error: Call to a member function getCfg() on a non-object in /var/www/bibelaabner.dk/public_html/administrator/components/com_comprofiler/plugin.foundation.php on line 3228

And it's the same error that I've now see other users of CB get when upgrading to 1.7 so I'm assuming that your CB version is out of date and if you updated it would get the same error. Perhaps not though. I'll wait to hear what your version is first before trying to help more.

As to the error I got, Line 3228 reads:

Code: Select all

$myLanguage=$mainframe->getCfg( 'language' );

mainframe was deprecated (http://en.wikipedia.org/wiki/Deprecation) in Joomla 1.5 and removed in 1.6, so it's unfair to blame Joomla's developers for someone using code that wasn't meant to be there in the first place. Before more people start hounding me, I'm not saying the CB Team is at fault. They have a single install package for Joomla 1.0, 1.5, 1.6 (and now 1.7) so that's 3 sets of api's that they have to account for so that's likely why it's there in the first place.

With that being said, as you can see things aren't as simple as it always appears to us the users. The Joomla team and the CB team are both extremely smart and good at what they do. When things get complicated like this (and if we don't know better), it's always best to ask why something was done rather than immediately blaming someone when you haven't heard their side (I've been guilty of this as well before).

In my opinion Joomla lost one point - the frist new-cycle-release simply failed.

Actually it was a great success and I'm proud of them

Kind regards,
Nick

[Beat]

Could someone from Joomla leadership team please explain what these two statements mean:

End of Life: Once a release has reached the end of its support lifetime (its “end of life” or EOL) it will no longer be maintained by the Joomla project teams for either stability or security issues.

Version 1.6.5 will reach end of life one month from today, on 19 August 2011.

As I understand in the above (and from e.g. Linux distributions), medium (like in 1.7.0) and high level security issues found in 1.6.x should trigger a new release 1.6.y same time as fixed in 1.7.z, if we are within life-cycle.

Otherwise, it means that 1.6 is already not supported anymore already now ?

Is a 1.6.6 release just fixing the medium-level XSS vulnerabilities of 1.6.5 (without the changes of 1.7.0) planed ?

[Webdongle]

Personally, I thought 'Short term Release' and 'Version 1.6.5 will reach end of life one month from today, on 19 August 2011.' were self explanatory. I still don't understand why there are short term releases. Unless they are 'Test beds' for trying different features that can be included in the ?

Throughout the forums I see advice for people with 1.5.23 sites to wait until the next LTS before upgrading.


With those upgrading to 1.7.0 I am seeing a pattern of mainly two things.

1. Trying to update to 1.7.0 from 1.6.4 or lower. There is a bug tracker for that and it appears that it's being looked into. http://joomlacode.org/gf/project/joomla ... m_id=26441
2. Poorly set up servers with Joomla not being allowed Ownership. But as you can see from message 4 of http://groups.google.com/group/joomlabu ... 532fef6c82 using the ftp layer works.

Jupgrade will upgrade easily (on properly configured servers) from 1.5.23 to 1.7.0. And when 1.8.0 (or whatever the next LTS is called) comes out then I can see no reason why Jupgrade will not work for that as well.

Nothing can be made completely fool proof and surely the Joomla developers can not be held responsible for :
Users who don't know how to configure their servers correctly
or
Decide to install a release with short term support then don't update regularly.


And it's just not the users. 1.7.0 RC1 was out a while before 1.7.0 stable was released but many 3rd party extension developers failed to test on it. The result being that users blame Joomla for the extensions not working.

The above is just a personal opinion and others may (or may not) agree with it.