 |
Never seen this error on the backend (after saving a content article) before I recently upgraded to 4.6.3
--------------------
Fatal error: Using $this when not in object context in /home/******/public_html/components/com_sef/joomsef.php on line 633
--------------------
Anyone seen it before/help?
Tks, John
|
New version of JoomS ...
|
Posted 9 years, 5 months ago
by Champenois
|
|
|
JoomSEF affected by both v.4.3.2 and v.4.4.0 breaks content out of page
Affects only single article pages, not category page/s
Browser latest Chrome + FF 18.02
PHP 5.3.15
Turn off JoomSEF, cannot break out content
Clear all caches, turn on JoomSEF, go to any article page, refresh, breaks out
Unbroken article source
-----------
</head>
<body class="site com_content view-article no-layout no-task itemid-136">
<!-- Body -->
<div class="body">
<div class="container">
<!-- Header -->
<div class="header">
-----------
Article page source after refresh - breaks >>
-----------
</head>
<body class="contentpane modal">
<div id="system-message-container">
<div id="system-message">
</div>
</div>
<div class="item-page">
<div class="page-header">
-----------
Please advise |
JoomSEF 4.3.2+ break ...
|
Posted 12 years, 1 month ago
by Champenois
|
|
|
Tks for the reply
As we paid for the extension, it would be extremely helpful if you would include an ETA of the fix release
Thank you
|
Update statistics re ...
|
Posted 12 years, 2 months ago
by Champenois
|
|
|
Running update statistics in JoomSEF results (first time) in the following error:
Fatal error: Call to undefined method JRegistry::loadINI() in /home/xxxxxx/public_html/administrator/components/com_sef/views/statistics/tmpl/default_statistics.php on line 73
Loading the statistics page (not running an update) now always results in the error
Joomla 3.02 / JoomSEF 4.3.0
File permissions also checked
|
Update statistics re ...
|
Posted 12 years, 2 months ago
by Champenois
|
|
|
Yes, but your bug fix statement was so non-specific that we've wasted a lot of time before realising it was in the content due to the misleading error statement your program generated.
Not to mention the not-insignificant amount of $NZ45 to follow up on your comment that you could fix it if we paid.
This has come down to a poor user experience which deserves mentioning on the product's joomla extension page, so no-one else gets to waste their time.
Tks for the prompt replies anyway.
|
JoomSEF4 breaks Joom ...
|
Posted 12 years, 2 months ago
by Champenois
|
|
|
ok, found it
I was setting up an article each time and linking it to the home page menu item
nothing else, even other extensions, bare bones install
so after sleeping on it, I looked closely at that article this morning
in it, there is embedded an old link (from a former site install)
<a href="index.php?option=com_contact&view=contact&catid=4&id=1-contact-us&Itemid=109">CONTACT us</a>
That's the problem
Why is JoomSEF running a non-existent SQL error on an out of date link and 404'ing the parent page?
This could happen at any time through backend article/contact etc deletions..
Obviously it wants to make an SEF link out of it, but isn't there a better way of handling this like ignoring it when a match can't be found? If it gets clicked on then a real 404 would occur.
Let's know and tks for the quick answers so far
Tks, John
I turned off "Display Errors" in php settings, just to be sure. |
JoomSEF4 breaks Joom ...
|
Posted 12 years, 2 months ago
by Champenois
|
|
|
This has been posted in the community area previously:
www.artio.net/support-forums/joomsef/com...t-page-404-sql-error
------------
Now paid/customer support
New J3.02 site, new host, no sample data, protostar, only one article page created for home page
No sample data = no contacts setup, no record in the contact_details table
SQL error on frontend with 404
Uninstalled free version, deleted .bak tables, reinstalled paid version (4)
Same error result
SQL=SELECT `id`, `alias` AS `name`, `catid`, `metakey`, `metadesc`, `metadata`, `language`,`misc` FROM `xxxxx_contact_details` WHERE `id` = 1-contact-us
Database Version 5.5.23-55
Database Collation utf8_general_ci
PHP Version 5.3.15
Web Server Apache
Safe Mode Off
Open basedir None
Display Errors On
Short Open Tags On
File Uploads On
Magic Quotes Off
Register Globals Off
Output Buffering Off
Session Save Path /tmp
Session Auto Start 0
XML Enabled Yes
Zlib Enabled Yes
Native ZIP Enabled Yes
Disabled Functions dl
Mbstring Enabled Yes |
JoomSEF4 breaks Joom ...
|
Posted 12 years, 2 months ago
by Champenois
|
|
|
hi there, no, it disappears if joomsef is turned off
the strange thing is that with joomsef turned on, and the meu item deleted out of the db and the contact item deleted (no other items in the contact_details table), it still runs the sql error (every cache possible deleted)
If I do a new install locally and install jooomsef NEXT, then create the contact item and menu item, there's no problem.
So there's either a bug in J3.02/conflict joomsef/server problem
tks for the help we may take up the paid suport, will do a newdom/install on the remote server mimicking the local process and see what happens first
have been posting here as a help to you as well as finding a solution
|
JoomSEF 4.3.0 result ...
|
Posted 12 years, 3 months ago
by Champenois
|
|
|
|
JoomSEF 4.3.0 result ...
|
Posted 12 years, 3 months ago
by Champenois
|
|
|
Deinstalled JoomSEF extension
removed _bak tables
Frontend ok
Created a new contact item
created a new main menu item for it
Frontend ok
Reinstalled JoomSEF, no errors
Turned on JoomSEF
Original error back again: SQL=SELECT `id`, `alias` AS `name`, `catid`, `metakey`, `metadesc`, `metadata`, `language`,`misc` FROM `xxxx_contact_details` WHERE `id` = 1-contact-us
If you think you can get this fixed, we'll buy priority support
|
JoomSEF 4.3.0 result ...
|
Posted 12 years, 3 months ago
by Champenois
|
|
|
apologies, I didn't do a very good job reporting the errors
on installing 4.3.0 first time on j3.02, there were 2 errors and I didn't record them so can only go from memory
1/ first was that .xml file could not be found and I think it actually said "joomla.xml"
2/ second was that "com_banners could not be removed"
I have looked around but can't figure out how to fix the link, there's no apparent way in the db menu table as the contact entry follows the same structure as all the other links.
I trashed the contact us link in main menu and alias link in top menu, db menu entry is not removed and error persists.
Removed the menu link manually from the db
Then removed the contact item in com_contacts backend
Item gone in db table "xxxx_contact_details"
SQL Error persists front end
Deleted all JoomSEF SEF's, SQL error persists
Cleared all chaches/tmp/browser cache, SQL front-end error persists
Turned off JoomSEF
Would have purchased the extension but no guarantee I'll get it working.
Anyway, the extra error info I've given may help you, tks
|
JoomSEF 4.3.0 result ...
|
Posted 12 years, 3 months ago
by Champenois
|
|
|
Joomla 3.02
JoomSEF = com_joomsef4-4.3.0.zip
New Install
Backend install error: cannot find xml file
No JoomSEF component menu item
Home-front-end runs 404 with error:
SQL=SELECT `id`, `alias` AS `name`, `catid`, `metakey`, `metadesc`, `metadata`, `language`,`misc` FROM `xxxx_contact_details` WHERE `id` = 1-contact-us
Uninstalled
Reinstalled
Now no backend error
Component menu item for JoomSEF now exists
but front-end 404 and sql error the same
|
JoomSEF 4.3.0 result ...
|
Posted 12 years, 3 months ago
by Champenois
|
|
More |
