-
AuthorPosts
-
March 23, 2009 at 4:15 pm #139491
I am currently rebuilding my blog site with the Avian II 1.5 modern template. I had used this template before the rebuild in Joomla 1.5.7. Now, after installing it successfully into a fresh install (new database and everything) of Joomla 1.5.9, I get the following error message when setting the template to my default:
Fatal error: Call to undefined function sefreltoabs() in /home/lhubbell/public_html/templates/ja_avian_ii_m/html/mod_login/default.php on line 58
I’ve also tried to do the Quickstart install, but that has been more problematic than this.
Please help! My blog has been down for two weeks now and I’m desperately trying to get it back up.
Thanks!
Arvind Chauhan ModeratorArvind Chauhan
- Join date:
- September 2014
- Posts:
- 3835
- Downloads:
- 74
- Uploads:
- 92
- Thanks:
- 1240
- Thanked:
- 1334 times in 848 posts
March 23, 2009 at 7:06 pm #297498If your Ja avian is not default? I mean does the site works with other installed template, such as Ja Purity as default?
If YES, then you need to turn on the legacy plugin, . May be you are trying to install template of older version (J 1.10.x) or did you just import your old JA Avian template folder to new installtion?
Try with legacy plugin on. You can find it in Extensions >> Plugin Manager >> legacy plugin. Publish it and try again.
What problems you faced with quickstart installation?
1 user says Thank You to Arvind Chauhan for this useful post
Arvind Chauhan ModeratorArvind Chauhan
- Join date:
- September 2014
- Posts:
- 3835
- Downloads:
- 74
- Uploads:
- 92
- Thanks:
- 1240
- Thanked:
- 1334 times in 848 posts
March 23, 2009 at 7:16 pm #297500<blockquote>Fatal error: Call to undefined function sefreltoabs() in /home/lhubbell/public_html/templates/ja_avian_ii_m/html/mod_login/default.php on line 58</blockquote>
Asked google about this error of yours, the closest i could get is this :
http://forum.joomla.org/viewtopic.php?f=428&t=380529&start=0 .
It reaffirms the doubts about template’s J .1.5.x legacy / native compatibility. Let us know if turning on legacy plugin helps.
1 user says Thank You to Arvind Chauhan for this useful post
March 23, 2009 at 8:32 pm #297509Thanks drarvindc, the legacy plugin worked. I appreciate it.
The problems I’ve had with the quickstart installation had a lot to do with admin lockout and database problems.
As I mentioned, I am rebuilding my blog from a very successful run using Joomla 1.5.7 and the Avian II template. Through an error of mine adding an additional site to my hosting account, I accidently uninstalled my blog. The hosting company had not backed up my site or database (that’s a whole other story).
So, I was diligently restoring my articles when I had finally finished importing all of my old content and artwork. The next morning, I went to log in and the site wouldn’t let me in.
I tried the phpAdmin trick and attempted to change the MD5 password, but to no avail. After several further attempts with newly created databases, I gave up using the quickstart method for installation. Every time I would complete the installation, I would get locked out–immediately. VERY frustrating to say the least.
This time, I did an installation using my hosting company’s Fantastico installer and let Joomla create a database for the site. So far, it’s working. I’m keeping my fingers crossed and praying these are the last of the problems.
Hopefully, I haven’t angered the Joomla gods and I can proceed peacefully:)
Arvind Chauhan ModeratorArvind Chauhan
- Join date:
- September 2014
- Posts:
- 3835
- Downloads:
- 74
- Uploads:
- 92
- Thanks:
- 1240
- Thanked:
- 1334 times in 848 posts
March 23, 2009 at 8:58 pm #297516<em>@lhubbell 119693 wrote:</em><blockquote>Thanks drarvindc, the legacy plugin worked. I appreciate it.
The problems I’ve had with the quickstart installation had a lot to do with admin lockout and database problems.
As I mentioned, I am rebuilding my blog from a very successful run using Joomla 1.5.7 and the Avian II template. Through an error of mine adding an additional site to my hosting account, I accidently uninstalled my blog. The hosting company had not backed up my site or database (that’s a whole other story).
So, I was diligently restoring my articles when I had finally finished importing all of my old content and artwork. The next morning, I went to log in and the site wouldn’t let me in.
I tried the phpAdmin trick and attempted to change the MD5 password, but to no avail. After several further attempts with newly created databases, I gave up using the quickstart method for installation. Every time I would complete the installation, I would get locked out–immediately. VERY frustrating to say the least.
This time, I did an installation using my hosting company’s Fantastico installer and let Joomla create a database for the site. So far, it’s working. I’m keeping my fingers crossed and praying these are the last of the problems.
Hopefully, I haven’t angered the Joomla gods and I can proceed peacefully:)</blockquote>
Thats a very strange scenario with quickstart installation. To the max i have witnessed is folder permission problems or database connection problems. Never got locked out of any of my sites so far, other than one but i was using JACL component and it locked me out the very moment i fingered it.
March 23, 2009 at 9:09 pm #297521In my rather brief experience, the database issue is VERY finicky in the Joomla sites.
I had a recent situation where I was building two personal Joomla sites simultaneously. Somehow, the information had gotten input wrong or something like that. I discovered both sites had the same name in the Global Config, so I tried to switch the database on one of them. Almost to moment I switched the database name, I got a fatal error and was locked out again. Had to reinstall that one again since I was just starting new anyway. Not doing that again!
Arvind Chauhan ModeratorArvind Chauhan
- Join date:
- September 2014
- Posts:
- 3835
- Downloads:
- 74
- Uploads:
- 92
- Thanks:
- 1240
- Thanked:
- 1334 times in 848 posts
March 23, 2009 at 9:21 pm #297526well if you ended up renaming the database. you could have changed the database setting name in the configuration.php manually.
here is the code from configuration.php, which could have been altered to save you from the trouble.
<blockquote>var $dbtype = ‘mysql’;
var $host = ‘localhost’;
var $user = ‘opal’;
var $db = ‘opal’;
var $dbprefix = ‘jos_’;
var $mailer = ‘mail’;</blockquote>1 user says Thank You to Arvind Chauhan for this useful post
-
AuthorPosts
This topic contains 7 replies, has 2 voices, and was last updated by Arvind Chauhan 15 years, 8 months ago.
We moved to new unified forum. Please post all new support queries in our New Forum