Support

UNiTE, Remote CLI, eXtract Wizard

#3540 Strict Standards error in kickstart - SOLVED

Posted in ‘UNiTE and Remote CLI’
This is a public ticket

Everybody will be able to see its contents. Do not include usernames, passwords or any other sensitive information.

Environment Information

PHP version
n/a
Tool
UNiTE
Tool version
n/a

Latest post by nicholas on Sunday, 04 October 2009 22:58 CDT

Tuesday, 08 September 2009 01:36 CDT

user6984
I installed new joomlapack and made backups as 1000 times before with previous versions. But when I try to start kickstart at my localhost (I use latest xampp on linux-Ubuntu) I get following messages:

Strict Standards: Redefining already defined constructor for class UnarchiverParent in /opt/lampp/htdocs/smrekovit/kickstart.php on line 565

Strict Standards: Non-static method Text::_() should not be called statically, assuming $this from incompatible context in /opt/lampp/htdocs/smrekovit/kickstart.php on line 2481

Strict Standards: Non-static method Language::getInstance() should not be called statically, assuming $this from incompatible context in /opt/lampp/htdocs/smrekovit/kickstart.php on line 409

Strict Standards: Non-static method Text::_() should not be called statically, assuming $this from incompatible context in /opt/lampp/htdocs/smrekovit/kickstart.php on line 2590

Strict Standards: Non-static method Language::getInstance() should not be called statically, assuming $this from incompatible context in /opt/lampp/htdocs/smrekovit/kickstart.php on line 409

Strict Standards: Non-static method Text::_() should not be called statically, assuming $this from incompatible context in /opt/lampp/htdocs/smrekovit/kickstart.php on line 2591

Strict Standards: Non-static method Language::getInstance() should not be called statically, assuming $this from incompatible context in /opt/lampp/htdocs/smrekovit/kickstart.php on line 409

Strict Standards: Non-static method Text::_() should not be called statically, assuming $this from incompatible context in /opt/lampp/htdocs/smrekovit/kickstart.php on line 2592

Strict Standards: Non-static method Language::getInstance() should not be called statically, assuming $this from incompatible context in /opt/lampp/htdocs/smrekovit/kickstart.php on line 409

Strict Standards: Non-static method Text::_() should not be called statically, assuming $this from incompatible context in /opt/lampp/htdocs/smrekovit/kickstart.php on line 2593

Strict Standards: Non-static method Language::getInstance() should not be called statically, assuming $this from incompatible context in /opt/lampp/htdocs/smrekovit/kickstart.php on line 409

Strict Standards: Non-static method Text::_() should not be called statically, assuming $this from incompatible context in /opt/lampp/htdocs/smrekovit/kickstart.php on line 2594

Strict Standards: Non-static method Language::getInstance() should not be called statically, assuming $this from incompatible context in /opt/lampp/htdocs/smrekovit/kickstart.php on line 409

Strict Standards: Non-static method Text::_() should not be called statically, assuming $this from incompatible context in /opt/lampp/htdocs/smrekovit/kickstart.php on line 2595

Strict Standards: Non-static method Language::getInstance() should not be called statically, assuming $this from incompatible context in /opt/lampp/htdocs/smrekovit/kickstart.php on line 409

Strict Standards: Non-static method Text::_() should not be called statically, assuming $this from incompatible context in /opt/lampp/htdocs/smrekovit/kickstart.php on line 2596

Strict Standards: Non-static method Language::getInstance() should not be called statically, assuming $this from incompatible context in /opt/lampp/htdocs/smrekovit/kickstart.php on line 409

Strict Standards: Non-static method Text::_() should not be called statically, assuming $this from incompatible context in /opt/lampp/htdocs/smrekovit/kickstart.php on line 2597

Strict Standards: Non-static method Language::getInstance() should not be called statically, assuming $this from incompatible context in /opt/lampp/htdocs/smrekovit/kickstart.php on line 409

Strict Standards: Non-static method Text::_() should not be called statically, assuming $this from incompatible context in /opt/lampp/htdocs/smrekovit/kickstart.php on line 2598

Strict Standards: Non-static method Language::getInstance() should not be called statically, assuming $this from incompatible context in /opt/lampp/htdocs/smrekovit/kickstart.php on line 409

Strict Standards: Non-static method Text::_() should not be called statically, assuming $this from incompatible context in /opt/lampp/htdocs/smrekovit/kickstart.php on line 2599

Strict Standards: Non-static method Language::getInstance() should not be called statically, assuming $this from incompatible context in /opt/lampp/htdocs/smrekovit/kickstart.php on line 409

Strict Standards: Non-static method Text::_() should not be called statically, assuming $this from incompatible context in /opt/lampp/htdocs/smrekovit/kickstart.php on line 2600

Strict Standards: Non-static method Language::getInstance() should not be called statically, assuming $this from incompatible context in /opt/lampp/htdocs/smrekovit/kickstart.php on line 409

Strict Standards: Non-static method Text::_() should not be called statically, assuming $this from incompatible context in /opt/lampp/htdocs/smrekovit/kickstart.php on line 2601

Strict Standards: Non-static method Language::getInstance() should not be called statically, assuming $this from incompatible context in /opt/lampp/htdocs/smrekovit/kickstart.php on line 409

Strict Standards: Non-static method Text::_() should not be called statically, assuming $this from incompatible context in /opt/lampp/htdocs/smrekovit/kickstart.php on line 2602

Strict Standards: Non-static method Language::getInstance() should not be called statically, assuming $this from incompatible context in /opt/lampp/htdocs/smrekovit/kickstart.php on line 409

Strict Standards: Non-static method Text::_() should not be called statically, assuming $this from incompatible context in /opt/lampp/htdocs/smrekovit/kickstart.php on line 2603

Strict Standards: Non-static method Language::getInstance() should not be called statically, assuming $this from incompatible context in /opt/lampp/htdocs/smrekovit/kickstart.php on line 409

Strict Standards: Non-static method Text::_() should not be called statically, assuming $this from incompatible context in /opt/lampp/htdocs/smrekovit/kickstart.php on line 2604

Strict Standards: Non-static method Language::getInstance() should not be called statically, assuming $this from incompatible context in /opt/lampp/htdocs/smrekovit/kickstart.php on line 409

Strict Standards: Non-static method Text::_() should not be called statically, assuming $this from incompatible context in /opt/lampp/htdocs/smrekovit/kickstart.php on line 2605

Strict Standards: Non-static method Language::getInstance() should not be called statically, assuming $this from incompatible context in /opt/lampp/htdocs/smrekovit/kickstart.php on line 409

Strict Standards: Non-static method Text::_() should not be called statically, assuming $this from incompatible context in /opt/lampp/htdocs/smrekovit/kickstart.php on line 2606

Strict Standards: Non-static method Language::getInstance() should not be called statically, assuming $this from incompatible context in /opt/lampp/htdocs/smrekovit/kickstart.php on line 409

Strict Standards: Non-static method Text::_() should not be called statically, assuming $this from incompatible context in /opt/lampp/htdocs/smrekovit/kickstart.php on line 2607

Strict Standards: Non-static method Language::getInstance() should not be called statically, assuming $this from incompatible context in /opt/lampp/htdocs/smrekovit/kickstart.php on line 409

Warning: Cannot modify header information - headers already sent by (output started at /opt/lampp/htdocs/smrekovit/kickstart.php:409) in /opt/lampp/htdocs/smrekovit/kickstart.php on line 2942

Warning: Cannot modify header information - headers already sent by (output started at /opt/lampp/htdocs/smrekovit/kickstart.php:409) in /opt/lampp/htdocs/smrekovit/kickstart.php on line 2943
JoomlaPack Kickstart 2.3.2
Backup Archive

Please select a ZIP/JPA file below and press the "Start" button.
 

Operation Method
AJAX (refreshless) JavaScript Redirects
Extraction Method

Write directly to files Use FTP

Restore file/directory permissions (JPA archives only)
FTP Options
Host 	
Port 	
Username 	
Password 	
Initial Directory 	
Stealth Mode

Stealth mode (restrict access only to your IP while restoring) 	
Stealth Mode redirection URL
(or leave blank to display a 403 Forbidden message to non authorized users) 	

 


Strict Standards: Non-static method Text::_() should not be called statically, assuming $this from incompatible context in /opt/lampp/htdocs/smrekovit/kickstart.php on line 2967

Strict Standards: Non-static method Language::getInstance() should not be called statically, assuming $this from incompatible context in /opt/lampp/htdocs/smrekovit/kickstart.php on line 409
Copyright ©2008-2009 JoomlaPack Developers.
Strict Standards: Non-static method Text::_() should not be called statically, assuming $this from incompatible context in /opt/lampp/htdocs/smrekovit/kickstart.php on line 2968

Strict Standards: Non-static method Language::getInstance() should not be called statically, assuming $this from incompatible context in /opt/lampp/htdocs/smrekovit/kickstart.php on line 409
JoomlaPack KickStart is Free Software, distributed under the terms of the GNU General Public License, version 2 or later.


Than I extract backup manualy and start installation process and still I get following errors:

Deprecated: Assigning the return value of new by reference is deprecated in /opt/lampp/htdocs/smrekovit/libraries/pattemplate/patTemplate.php on line 1424

Deprecated: Assigning the return value of new by reference is deprecated in /opt/lampp/htdocs/smrekovit/libraries/pattemplate/patErrorManager.php on line 202


I tried to install fresh joomla as well and it works fine.

Please help.

Tuesday, 08 September 2009 03:27 CDT

dlb
What version of php are you using? Neither Joomla! nor JoomlaPack is compatible with php 5.3. I know 5.3 is available in Debian Squeeze, I can't imagine that Ubuntu would have added it yet, but the "depreciated" messages occur with 5.3.


Dale L. Brackin
Support Specialist


us.gifEnglish: native


Please keep in mind my timezone and cultural differences when reading my replies. Thank you!


????
My time zone is EST (UTC -5) (click here to see my current time in Philadelphia, PA)

Tuesday, 08 September 2009 08:51 CDT

nicholas
Furthermore, I can't work around the "Strict Standards" notices without braking PHP4 support. Believe it or not, there are still many people on PHP4 and I can't leave them out on the cold. I will, eventually, but not just yet.

The second batch of errors (appearing either in JPI3 or in Joomla! itself) are the result of Joomla! not being compatible with PHP 5.3. Yes, even JPI3 makes use of the standard Joomla! libraries. So, for now, either use the latest PHP 5.2.x or set your PHP error reporting to a much lower level in php.ini. In the latter case, be warned that Joomla! behavior will range from funky to outright broken. As I said, Joomla! IS NOT compatible with PHP 5.3 yet. There is ongoing work to achieve this, but it's still "not there" yet.

Nicholas K. Dionysopoulos

Lead Developer and Director

🇬🇷Greek: native 🇬🇧English: excellent 🇫🇷French: basic • 🕐 My time zone is Europe / Athens
Please keep in mind my timezone and cultural differences when reading my replies. Thank you!

Wednesday, 09 September 2009 08:04 CDT

user6984
Thanks for answers. It is true: xampp (lampp) uses php 5.3. But I still doesnt understand why fresh joomla install works?

Secondly I have no Idea how to set xampp to earlier version of php. I am pretty new on working with virtual server (semi new on joomla!).

Any help?

Wednesday, 09 September 2009 23:19 CDT

nicholas
Unfortunately, XAMPP doesn't offer a downgrade procedure for its PHP installation. You can, however, do one of the following:
1. Download the ZIP binary distribution of PHP and extract it inside XAMPP's PHP directory. This should work in principle, I have not tested it myself.
2. Use WampServer. It does use PHP 5.3.0, but you can download the PHP 5.2.9-2 self-installable package, then click on WampServer's tray icon, go to PHP and select PHP 5.2.9 instead of the default PHP 5.3.0. I have personally tested this and it's working.

About your comment with fresh Joomla! installation, I think that the fresh Joomla! installation doesn't make use of any menu items etc which conflict with PHP 5.3.0. If you try to add articles and administer this blank site, you'll witness the PHP 5.3.0 hell.

As a side note, Joomla! 1.5.15 will support PHP 5.3.0 without any workarounds, however you'll have to lower the error reporting level to "Simple" or "None", otherwise you'll experience Strict Standards notices. The source of these notices is the PHP 4 compatibility we, as developers, are forced to maintain on our software. When hosts decide to ditch PHP 4, we'll be able to move on and get rid of those notices as well.

Nicholas K. Dionysopoulos

Lead Developer and Director

🇬🇷Greek: native 🇬🇧English: excellent 🇫🇷French: basic • 🕐 My time zone is Europe / Athens
Please keep in mind my timezone and cultural differences when reading my replies. Thank you!

Thursday, 10 September 2009 00:58 CDT

user6984
Hi. I somehow managed to get lamp working in ubuntu (through synaptic) and the errors are gone. Ubuntu doesnt use php 5.3, so the problem is php 5.3 for sure.

Now I have different problem. Css doesnt seems to appear right.
I use http://localhost/mysite/ path. And .htaccess rewrite base is set to /mysite/

Should I open new topic or shall we continue there?

Thursday, 10 September 2009 04:57 CDT

dlb
The css problem is probably caused because your $live_site variable in the configuration.php file is blank. Edit configuration.php and add your site url (localhost/mysite) to the $live_site variable.

The new thread/same thread question is a tough one. If I figure it out, I'll let you know. :lol:


Dale L. Brackin
Support Specialist


us.gifEnglish: native


Please keep in mind my timezone and cultural differences when reading my replies. Thank you!


????
My time zone is EST (UTC -5) (click here to see my current time in Philadelphia, PA)

Thursday, 10 September 2009 08:24 CDT

user6984
I set livesite like you said,
tried to disable .htaccess.
Disabled sh404sef as well
cache of smart optimizer went to trash
shortly; everything

still no change on my frontend. Just for information backend is OK completly.

Previous times I used joomlapack, every such problem was connected with sh404sef cache or .htaccess

Any more ideas?

Thursday, 10 September 2009 18:33 CDT

dlb
The "no css" really sounds like a $live_site problem. The one that I found on this machine was 'http://localhost/joomla'. I didn't remember the "http://" earlier.


Dale L. Brackin
Support Specialist


us.gifEnglish: native


Please keep in mind my timezone and cultural differences when reading my replies. Thank you!


????
My time zone is EST (UTC -5) (click here to see my current time in Philadelphia, PA)

Tuesday, 15 September 2009 08:58 CDT

user6984
It realy isnt live_site problem. I changed it and site remains the same. There must be different problem.

Maybe something with smartoptimizer?

And sorry for late response (lack of time - children :))

p.s.
administration (backend) is OK

Tuesday, 15 September 2009 12:49 CDT

dlb
I like Kunena less and less. :x

http : / / is a magic word that the forum software strips out. A useless feature at best, very very bad for a technical support environment. I was trying to tell you that I found that protocol string as part of my $live_site variable on my old site.

I'll flag this for Nicholas to see if he has a different suggestion.


Dale L. Brackin
Support Specialist


us.gifEnglish: native


Please keep in mind my timezone and cultural differences when reading my replies. Thank you!


????
My time zone is EST (UTC -5) (click here to see my current time in Philadelphia, PA)

Wednesday, 16 September 2009 01:01 CDT

nicholas
I think that Dale is correct. I don't understand what "smartoptimizer" refers to. If you're talking about SEO URL's then, yes, this may be the problem. Try turning it off to see if your site works, but only after you have changed the live_site parameter in configuration.php.

Nicholas K. Dionysopoulos

Lead Developer and Director

🇬🇷Greek: native 🇬🇧English: excellent 🇫🇷French: basic • 🕐 My time zone is Europe / Athens
Please keep in mind my timezone and cultural differences when reading my replies. Thank you!

Thursday, 17 September 2009 09:34 CDT

user6984
Found a solution. In my templates index I needed to change link to css files. Strange It works ok on the startlogic server.

Thursday, 17 September 2009 16:39 CDT

dlb
Paths and permissions are the two things that give you grief on a new server. I'm glad you got it fixed. :D


Dale L. Brackin
Support Specialist


us.gifEnglish: native


Please keep in mind my timezone and cultural differences when reading my replies. Thank you!


????
My time zone is EST (UTC -5) (click here to see my current time in Philadelphia, PA)

Saturday, 03 October 2009 09:44 CDT

user7184
Hi Folks,

just to give a little back, here are my 2 Cents abut this topic:

If you want to use the XAMP-Environment for testing with JoomlaPack, use V. 1.7 !

This one works and doesn't throw any errors, as the afore mentioned ones.

To get the older Version, you just have to take a little care, whilst clicking through the apache friend's site.
Somewhere a link for older versions on the sourceforge site of this project is displayed.
You use this or browse sourceforge; get V. 1.7 and go testing ...

Best Regards

MX

Sunday, 04 October 2009 22:58 CDT

nicholas
Be aware that XAMPP 1.7 is using PHP 5.3.0. As of Joomla! 1.5.14, this may cause trouble with menu items not working, "component not found" errors and the like. These will be addressed in Joomla! 1.5.15. JoomlaPack should work, YMMV.

Nicholas K. Dionysopoulos

Lead Developer and Director

🇬🇷Greek: native 🇬🇧English: excellent 🇫🇷French: basic • 🕐 My time zone is Europe / Athens
Please keep in mind my timezone and cultural differences when reading my replies. Thank you!

Support Information

Working hours: We are open Monday to Friday, 9am to 7pm Cyprus timezone (EET / EEST). Support is provided by the same developers writing the software, all of which live in Europe. You can still file tickets outside of our working hours, but we cannot respond to them until we're back at the office.

Support policy: We would like to kindly inform you that when using our support you have already agreed to the Support Policy which is part of our Terms of Service. Thank you for your understanding and for helping us help you!