Install Joomla 1.5

579 views
Skip to first unread message

Davy Gunarso

unread,
May 1, 2013, 4:57:23 AM5/1/13
to joomla-de...@googlegroups.com

I tried to install Joomla 1.5 which I downloaded from joomla.org, I wonder why I receive this error messages:

Strict Standards: Non-static method JLoader::import() should not be called statically in C:\xampp\htdocs\Joomla_15\libraries\joomla\import.php on line 29

Strict Standards: Non-static method JLoader::register() should not be called statically in C:\xampp\htdocs\Joomla_15\libraries\loader.php on line 71

Strict Standards: Non-static method JLoader::import() should not be called statically in C:\xampp\htdocs\Joomla_15\libraries\joomla\import.php on line 32

Strict Standards: Non-static method JLoader::register() should not be called statically in C:\xampp\htdocs\Joomla_15\libraries\loader.php on line 71

Strict Standards: Non-static method JLoader::load() should not be called statically in C:\xampp\htdocs\Joomla_15\libraries\loader.php on line 161

Strict Standards: Non-static method JLoader::register() should not be called statically in C:\xampp\htdocs\Joomla_15\libraries\loader.php on line 138

Strict Standards: Non-static method JRequest::clean() should not be called statically in C:\xampp\htdocs\Joomla_15\libraries\joomla\import.php on line 33

Strict Standards: Non-static method JRequest::_cleanArray() should not be called statically in C:\xampp\htdocs\Joomla_15\libraries\joomla\environment\request.php on line 463

Strict Standards: Non-static method JRequest::_cleanArray() should not be called statically in C:\xampp\htdocs\Joomla_15\libraries\joomla\environment\request.php on line 464

Strict Standards: Non-static method JRequest::_cleanArray() should not be called statically in C:\xampp\htdocs\Joomla_15\libraries\joomla\environment\request.php on line 465

Strict Standards: Non-static method JRequest::_cleanArray() should not be called statically in C:\xampp\htdocs\Joomla_15\libraries\joomla\environment\request.php on line 466

Strict Standards: Non-static method JRequest::_cleanArray() should not be called statically in C:\xampp\htdocs\Joomla_15\libraries\joomla\environment\request.php on line 467

Strict Standards: Non-static method JRequest::_cleanArray() should not be called statically in C:\xampp\htdocs\Joomla_15\libraries\joomla\environment\request.php on line 468

Strict Standards: Non-static method JLoader::import() should not be called statically in C:\xampp\htdocs\Joomla_15\libraries\joomla\import.php on line 35

Strict Standards: Non-static method JLoader::register() should not be called statically in C:\xampp\htdocs\Joomla_15\libraries\loader.php on line 71

Strict Standards: Non-static method JLoader::import() should not be called statically in C:\xampp\htdocs\Joomla_15\libraries\joomla\import.php on line 38

brian teeman

unread,
May 1, 2013, 5:35:34 AM5/1/13
to joomla-de...@googlegroups.com
Hi Davy 

Sorry, I don't mean to step on any toes, but this list is for extension 
development and discussion of how to create extensions.  You should 
instead ask this question on the Joomla forum.  Here's the direct link to 
it: 
http://forum.joomla.org/ 

Hope this helps! 

Kind regards, 
Brian

Donald Gilbert

unread,
May 1, 2013, 9:06:35 AM5/1/13
to joomla-de...@googlegroups.com
If you are required to use 1.5 for something specific, be aware that the problems you are experiencing is because you are installing it on a server that is running PHP 5.4.x. I know because I am dealing with similar errors on several new sites on a server with PHP 5.4.

So, if you are stuck on that server, I would suggest using at least 2.5, as it takes care of most of those issues (although there are several poorly coded extensions that fail miserably). If you can get off that version of PHP and back onto something like 5.2.17, then you can use 1.5 no problem, except you won't be getting any security updates, and it's getting hard to find extensions.


On Wed, May 1, 2013 at 4:06 AM, rahul borole <rbor...@gmail.com> wrote:
You should download latest version 2.5 or 3 as 1.5 is out of life
--
You received this message because you are subscribed to the Google Groups "Joomla! General Development" group.
To unsubscribe from this group and stop receiving emails from it, send an email to joomla-dev-gene...@googlegroups.com.
To post to this group, send an email to joomla-de...@googlegroups.com.
Visit this group at http://groups.google.com/group/joomla-dev-general?hl=en-GB.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

Amy Stephen

unread,
May 1, 2013, 10:32:30 AM5/1/13
to joomla-de...@googlegroups.com



On Wed, May 1, 2013 at 3:57 AM, Davy Gunarso <dav...@yahoo.com> wrote:


I tried to install Joomla 1.5 which I downloaded from joomla.org, I wonder why I receive this error messages:


Davy - do you remember where you downloaded 1.5? (And, if so, would you please share that link?) Just hoping there isn't an outdated download link that might be accidentally leading folks to EOL software.

Thanks!

Matt Thomas

unread,
May 1, 2013, 10:50:32 AM5/1/13
to Joomla! General Development
FWIW, the first Google result for "Joomla 1.5 download" is http://www.joomla.org/announcements/release-news/5419-joomla-1526-released.html, which has a direct link to the files. Should the release announcements by edited to remove those links? (not suggesting, but merely asking)

Best,

Matt Thomas
Founder betweenbrain
Phone: 203.632.9322
Twitter: @betweenbrain



--

Amy Stephen

unread,
May 1, 2013, 11:06:12 AM5/1/13
to joomla-de...@googlegroups.com
Wow. Had not considered that, Matt. That's a good question.

Niels Braczek

unread,
May 1, 2013, 11:36:56 AM5/1/13
to joomla-de...@googlegroups.com
Am 01.05.2013 16:50, schrieb Matt Thomas:

> FWIW, the first Google result for "Joomla 1.5 download" is http://www.joomla
> .org/announcements/release-news/5419-joomla-1526-released.html, which has a
> direct link to the files. Should the release announcements by edited to
> remove those links? (not suggesting, but merely asking)

Don't think so. Sometimes it can be vital to find old versions. Consider
this scenario:

An outdated website is running Joomla! 1.0.7, which has some
customization hacks (of course not documented). Now a freelancer has to
migrate to a current Joomla! version, preserving *any* existing
functionality (not documented, too). This happens quite frequently with
varying versions. Having an *original* 1.0.7 allows the freelancer to
re-engineer the requirements using a diff between the hacked and the
clean version.

So, access to old versions should always be possible.

Regards,
Niels

--
| http://barcamp-wk.de · 3. Barcamp Westküste · Frühjahr 2014 |
| http://www.bsds.de · BSDS Braczek Software- und DatenSysteme |
| Webdesign · Webhosting · e-Commerce · Joomla! Content Management |
------------------------------------------------------------------

Amy Stephen

unread,
May 1, 2013, 12:13:11 PM5/1/13
to joomla-de...@googlegroups.com
In the past when I was doing communication for the project, we kept older versions on Joomlacode but those versions were accessible only if you were logged on. The thinking was that someone who might require older copies is more likely to know where the project keeps versions (and what is and is not supported), more importantly, it helps guard against accident downloading old software by those who are not aware.


Sivasankar Chejarla

unread,
May 1, 2013, 8:51:01 AM5/1/13
to joomla-de...@googlegroups.com
You got this error because the functions some deprecated that not
suited with the current version of php 5.0,6.0 so better you can
download latest versions joomla 2.5 or 3.0
like......................................................joomla 1.5
is out dated..

(siva)

On 5/1/13, rahul borole <rbor...@gmail.com> wrote:
> You should download latest version 2.5 or 3 as 1.5 is out of life
>
> On Wednesday, 1 May 2013 14:27:23 UTC+5:30, Davy Gunarso wrote:
>>
>>
>> I tried to install Joomla 1.5 which I downloaded from joomla.org, I
>> wonder why I receive this error messages:
>>
>> *Strict Standards*: Non-static method JLoader::import() should not be
>> called statically in *
>> C:\xampp\htdocs\Joomla_15\libraries\joomla\import.php* on line *29*
>>
>> *Strict Standards*: Non-static method JLoader::register() should not be
>> called statically in *C:\xampp\htdocs\Joomla_15\libraries\loader.php* on
>> line *71*
>>
>> *Strict Standards*: Non-static method JLoader::import() should not be
>> called statically in *
>> C:\xampp\htdocs\Joomla_15\libraries\joomla\import.php* on line *32*
>>
>> *Strict Standards*: Non-static method JLoader::register() should not be
>> called statically in *C:\xampp\htdocs\Joomla_15\libraries\loader.php* on
>> line *71*
>>
>> *Strict Standards*: Non-static method JLoader::load() should not be
>> called statically in *C:\xampp\htdocs\Joomla_15\libraries\loader.php* on
>> line *161*
>>
>> *Strict Standards*: Non-static method JLoader::register() should not be
>> called statically in *C:\xampp\htdocs\Joomla_15\libraries\loader.php* on
>> line *138*
>>
>> *Strict Standards*: Non-static method JRequest::clean() should not be
>> called statically in *
>> C:\xampp\htdocs\Joomla_15\libraries\joomla\import.php* on line *33*
>>
>> *Strict Standards*: Non-static method JRequest::_cleanArray() should not
>> be called statically in *
>> C:\xampp\htdocs\Joomla_15\libraries\joomla\environment\request.php* on
>> line *463*
>>
>> *Strict Standards*: Non-static method JRequest::_cleanArray() should not
>> be called statically in *
>> C:\xampp\htdocs\Joomla_15\libraries\joomla\environment\request.php* on
>> line *464*
>>
>> *Strict Standards*: Non-static method JRequest::_cleanArray() should not
>> be called statically in *
>> C:\xampp\htdocs\Joomla_15\libraries\joomla\environment\request.php* on
>> line *465*
>>
>> *Strict Standards*: Non-static method JRequest::_cleanArray() should not
>> be called statically in *
>> C:\xampp\htdocs\Joomla_15\libraries\joomla\environment\request.php* on
>> line *466*
>>
>> *Strict Standards*: Non-static method JRequest::_cleanArray() should not
>> be called statically in *
>> C:\xampp\htdocs\Joomla_15\libraries\joomla\environment\request.php* on
>> line *467*
>>
>> *Strict Standards*: Non-static method JRequest::_cleanArray() should not
>> be called statically in *
>> C:\xampp\htdocs\Joomla_15\libraries\joomla\environment\request.php* on
>> line *468*
>>
>> *Strict Standards*: Non-static method JLoader::import() should not be
>> called statically in *
>> C:\xampp\htdocs\Joomla_15\libraries\joomla\import.php* on line *35*
>>
>> *Strict Standards*: Non-static method JLoader::register() should not be
>> called statically in *C:\xampp\htdocs\Joomla_15\libraries\loader.php* on
>> line *71*
>>
>> *Strict Standards*: Non-static method JLoader::import() should not be
>> called statically in *
>> C:\xampp\htdocs\Joomla_15\libraries\joomla\import.php* on line *38*

Niels Braczek

unread,
May 1, 2013, 2:11:11 PM5/1/13
to joomla-de...@googlegroups.com
Am 01.05.2013 18:13, schrieb Amy Stephen:

> In the past when I was doing communication for the project, we kept older
> versions on Joomlacode but those versions were accessible only if you were
> logged on. The thinking was that someone who might require older copies is
> more likely to know where the project keeps versions (and what is and is
> not supported), more importantly, it helps guard against accident
> downloading old software by those who are not aware.

It's ok to require a login. I just don't want the old versions being
removed.

Herman Peeren

unread,
May 1, 2013, 4:15:27 PM5/1/13
to joomla-de...@googlegroups.com, nbra...@bsds.de
All tags are in the SVN. I guess the old SVN wil never be deleted; it contains a lot of interesting historical info. If I'm not mistaken (I'm not sure of this at all, so please correct me) you only checkout a specific tag/version and the rest stays in the SVN-repo. Unlike Git, where you can clone the whole repo, including the whole history, all tags, versions, branches. In the CMS-GIT-repo tags are present from 1.7.3, but not the older history.

If the above is correct, then it might be useful to make a little script to get the old tagged versions from SVN and put them in a git-repo. It is not all info about all commits, but it is a handy and usefull container for all older tagged versions. Would there be any interest in such a historic tagged git-version? Or is there an easier way than a script looping through the tags in the SVN and chicking those versions out?

Old SVN's preserving all commits could once be valuable for investigations by software historians/archeologists. Maybe. But maybe I should just learn not to keep everything I collect and throw away more.

Nick Savov

unread,
May 1, 2013, 5:56:01 PM5/1/13
to joomla-de...@googlegroups.com
Good questions!

The main issue with putting them behind a password protected area is that
they would be very hard to find for many users. A lot of users are still
on J 1.5.20 range and they are usually recommended to upgrade to Joomla
1.5.26, then migrate to Joomla 3 or 2.5.

The other big issue is that it would be a lot of work to go back and make
all those changes. I guess if someone really wanted to do that, great!
But there's probably bigger fish to fry.

My 2 cents.

Kind regards,
Nick
>> | http://barcamp-wk.de � 3. Barcamp Westk�ste � Fr�hjahr 2014 |

Herman Peeren

unread,
May 2, 2013, 4:07:41 AM5/2/13
to joomla-de...@googlegroups.com, nbra...@bsds.de
BTW you don't need to be logged in to go to
http://joomlacode.org/gf/project/joomla/scmsvn/?action=browse&path=%2Fdevelopment%2Ftags%2F
and find all old versions from 1.0 onwards under that.
With SVN you can checkout that version; no login needed too.

Herman Peeren

unread,
May 2, 2013, 4:29:59 AM5/2/13
to joomla-de...@googlegroups.com
The explanation is: in PHP5 we explicitly declare a method as static, where in PHP4 that static keyword did not exist yet. If the error reporting level is strict, then you'll get these warnings. If you have to run Joomla 1.5 on that server, with the current configuration, you can try to diminish the error reporting level. You can do that in your php.ini

error_reporting = E_ALL & ~E_NOTICE

or if that is not editable by you, you could try to call error_reporting() in your first index.php.
Also see: http://forum.joomla.org/viewtopic.php?p=2412490
(which is on the forum and Brian is right, of course, that that is the proper place to ask questions like this. Sorry for answering it here).
Reply all
Reply to author
Forward
0 new messages