test melih
 melih
Viewing 13 posts - 16 through 28 (of 28 total)
  • Author
    Posts
  • HeR0 Friend
    #451996

    Hi
    I fixed it on http://www.hobbykwekers.nl/ but not http://www.hobbykwekers.nl/home/links/index
    they have difference. I used account ftp that you provided and i think that i fixed for http://www.hobbykwekers.nl
    Do you know why the difference ?

    Regards

    hobbykwekers Friend
    #452011

    Hi,

    The problem isn’t solved for the frontpage, this error appears after your fix (before the fix there are no errors on the frontpage, only on the link page, the fix actually makes things worse for the frontpage):

    The errors appeared after the 2.5.2 update. It was working fine on the 2.5.1 version. Why it isn’t working???? No idea, it must be something that was altered when updating the template from 2.5.1 to 2.5.2.

    Normally I test my site before upgrading but all seemed to work fine, I just missed the errors in the link section. It is the only component not working with this template, the rest of the site is fine.


    1. frontpage-hobbykwekers
    hobbykwekers Friend
    #452088

    ps. I removed your fix to remove the error on my front page.

    HeR0 Friend
    #452118

    Hi Hobbykwekrs

    I think that if you have the issue in future, you should set error_reporting = E_ALL & ~E_STRICT in php.ini, that should be able to solve the problem most effectively.

    HeR0 Friend
    #452119

    Have a nice day, let me known if you have further issues, i shall have a look and help you

    Regards,

    hobbykwekers Friend
    #452925

    Ok, problem solved! Putting the code in php.ini didn’t work. My webhost was so generous to take look. The component overwrites this line of code….we had to put it inside the code of the component itself.

    jga159 Friend
    #455860

    <em>@hobbykwekers 319569 wrote:</em><blockquote>Ok, problem solved! Putting the code in php.ini didn’t work. My webhost was so generous to take look. The component overwrites this line of code….we had to put it inside the code of the component itself.</blockquote>

    Hi hobbykwekers,
    could you precise in wich component exactly you have done the modification?

    because i have the same problem on localhost with UwAmp v2.1 as soon as i install JAT3 Plugin V2.5.0 running under joomla v2.5.4
    i have these damned message >:(
    Strict standards: Non-static method T3Common::node_attributes() should not be called statically, assuming $this from incompatible context in C:UwAmpwwwaspcje254pluginssystemjat3jat3coretemplate.php on line 1392
    thanks in advance

    jga159 Friend
    #456144

    Hello evrybody,

    the best way to stop these “damned message” is in Uwamp control console to set PHP Setting parameter “Display startup errors to “off” .
    it is strongly recommended to keep display_startup_errors off except for debugging!


    1. Capturer-display-startup-errors
    Ninja Lead Moderator
    #456421

    <em>@jga159 323382 wrote:</em><blockquote>
    Strict standards: Non-static method T3Common::node_attributes() should not be called statically, assuming $this from incompatible context in C:UwAmpwwwaspcje254pluginssystemjat3jat3coretemplate.php on line 1392</blockquote>

    This is a bug on your system, if you disabled notify error on your site >> its not best way to fix it. Please send me login info of your site. I shall check and help you fix it.

    billgertz Friend
    #458098

    Hi. I downloaded xampp 1.7.7 and installed JA Mendozite for Joomla 2.5 (18.42 MB) to make sure everyhing will be there. somehow, im getting this error.

    ATTACH=CONFIG]21917

    what is causing this issue? is something wrong with my PC or on the template? somehow, other template works but not the JA template.


    1. Bugmen0t
    HeR0 Friend
    #458121

    Hi Billgertz
    Please open file php.ini then find “error_reporting =” then replace to “error_reporting = E_ALL & ~E_NOTICE & ~E_STRICT”
    Path: xamppapachebinphp.ini ( may be difference with other version so you should search file php.ini in xampp folder )
    Regards,

    Ninja Lead Moderator
    #458132

    Hi billgertz,

    I have tested xampp 1.7.7 version and saw “Strict Standards” error notification the same your mention. Don’t worry because some scripts on our system are compatible with old php version. If you want to show this notification, you can config error_reporting=off on localhost site or your can change “static function” to “object”

    For example:
    <blockquote>T3Path:: path() -> call by case static function</blockquote>
    You need to change call by case object
    <blockquote>$jat3fw = new T3Path;
    $jat3fw->path();</blockquote>

    I raised this error to dev team: http://pm.joomlart.com/browse/JAECPLGTIIIJOOMLAIVI-469

    I will let you know it is done.

    Regards

    billgertz Friend
    #458305

    <em>@Ninja Lead 326312 wrote:</em><blockquote>Hi billgertz,

    I have tested xampp 1.7.7 version and saw “Strict Standards” error notification the same your mention. Don’t worry because some scripts on our system are compatible with old php version. If you want to show this notification, you can config error_reporting=off on localhost site or your can change “static function” to “object”

    For example:

    You need to change call by case object

    I raised this error to dev team: http://pm.joomlart.com/browse/JAECPLGTIIIJOOMLAIVI-469

    I will let you know it is done.

    Regards</blockquote>

    Thanks. I shall wait until it’s done. I’ll call it by subject for now. 🙂

Viewing 13 posts - 16 through 28 (of 28 total)

This topic contains 28 replies, has 5 voices, and was last updated by  billgertz 12 years, 7 months ago.

We moved to new unified forum. Please post all new support queries in our New Forum