-
AuthorPosts
-
zao dao Friend
zao dao
- Join date:
- September 2014
- Posts:
- 155
- Downloads:
- 160
- Uploads:
- 2
- Thanks:
- 12
- Thanked:
- 11 times in 1 posts
July 13, 2011 at 5:06 am #166235i install ja rave 1.6,and today the joomla.org release a joomla1.6.5 to 1.7 package
http://www.joomla.org/announcements/release-news/5379-joomla-17-rc1-released.html
http://joomlacode.org/gf/project/joomla/frs/?action=FrsReleaseView&release_id=15233when i upgrade by usingJoomla_1.6.5_to_1.7.0_RC1_Update.zip ,the frontpage show
Fatal error: Cannot instantiate abstract class JDatabaseQuery in D:xampphtdocsolpluginssystemjat3jat3corejoomlamodulehelper.php on line 292www.8media.com
www.zaodao.comzao dao Friendzao dao
- Join date:
- September 2014
- Posts:
- 155
- Downloads:
- 160
- Uploads:
- 2
- Thanks:
- 12
- Thanked:
- 11 times in 1 posts
July 14, 2011 at 8:11 am #401106find the answer
http://groups.google.com/group/joomla-dev-general/browse_thread/thread/5f18d884338e647a.?pli=1
JDatabaseQuery is now abstract due of the work done to support new
database engines (Windows Azure and Microsoft SQL Server). This means
you must use $db->getQuery(true); to instantiate a query as is the
correct practice in Joomla 1.6.The correct, advertised way to use JDatabaseQuery in 1.6 was:
$db = JFactory::getDbo();
$query = $db->getQuery(true);The following incorrect practice will no longer work in 1.7.
$db = JFactory::getDbo();
$query = new JDatabaseQuery;Developers of 1.6 extensions are advised to upgrade their code
immediately to the correct format (which will work fine in both Joomla
1.6 and 1.7).Wiki page has been updated:
www.8media.com
www.zaodao.com1 user says Thank You to zao dao for this useful post
sakoman Friendsakoman
- Join date:
- January 2007
- Posts:
- 21
- Downloads:
- 0
- Uploads:
- 0
- Thanks:
- 4
- Thanked:
- 2 times in 1 posts
July 21, 2011 at 8:58 pm #402390I’m not sure why this is marked as a solved problem!
There is still an issue with Joomla 1.7 and JA Rave as shipped.
Is there a particular file that one can edit to implement the recommended code fix?
Phill ModeratorPhill
- Join date:
- February 2014
- Posts:
- 7013
- Downloads:
- 40
- Uploads:
- 77
- Thanks:
- 917
- Thanked:
- 2206 times in 1818 posts
July 21, 2011 at 9:14 pm #402395This is not solved because JA have not yet released their templates as J1.7 compatible. Please do not upgrade until they are released.
sakoman Friendsakoman
- Join date:
- January 2007
- Posts:
- 21
- Downloads:
- 0
- Uploads:
- 0
- Thanks:
- 4
- Thanked:
- 2 times in 1 posts
July 21, 2011 at 11:13 pm #402409There will likely be a lot of folks updating since a Joomla security alert went out a couple of days ago recommending an immediate update to 1.7 to fix a security issue.
Phill ModeratorPhill
- Join date:
- February 2014
- Posts:
- 7013
- Downloads:
- 40
- Uploads:
- 77
- Thanks:
- 917
- Thanked:
- 2206 times in 1818 posts
July 22, 2011 at 7:11 am #402462Personally I think that alert is extremely unfair thing for the Joomla team to have done. They should be fixing J1.6.x rather than trying to force the update to J1.7 so quickly. IMHO it is very unfair on all the extension developers, especially the ones who do it as a hobby, out there to be forced to update their work at the drop of a hat.
It is especially wrong in my mind as by not fixing their problem Joomla.org are effectively ending their support for their own project 1 month early.
-
AuthorPosts
This topic contains 7 replies, has 3 voices, and was last updated by sakoman 13 years, 3 months ago.
We moved to new unified forum. Please post all new support queries in our New Forum