test
Viewing 4 posts - 1 through 4 (of 4 total)
  • Author
    Posts
  • schemedia Friend
    #839649

    hello
    the site I am working on was recently compromised so we moved it to a new server. unfortunately, that server only offered php 5.6.14 and I believe that may be causing some deprecation warnings when using the k2 filter component. the site is using joomla 3.2.3 and I am unable to upgrade it because of some major customizations that were done. I renewed my subscription today hoping a newer version would fix the issue, but it’s still showing the warnings. is there a way I can turn off the deprecation warnings? the search seems to work even with those, so I am hoping it is something easily hidden.

    here is an example of the warnings:
    Deprecated: Non-static method modK2FilterHelper::pull() should not be called statically, assuming $this from incompatible context in …./plugins/system/k2filter/K2Filter/models/itemlistfilter.php on line 1017

    Deprecated: Non-static method JApplicationSite::getMenu() should not be called statically, assuming $this from incompatible context in …./plugins/system/k2filter/K2Filter/views/itemlist/view.html.php on line 585

    Deprecated: Non-static method JApplicationCms::getMenu() should not be called statically, assuming $this from incompatible context in …./libraries/cms/application/site.php on line 250

    Deprecated: Non-static method JApplicationSite::getMenu() should not be called statically, assuming $this from incompatible context in …./plugins/system/k2filter/K2Filter/views/itemlist/view.html.php on line 680

    thanks
    robb

    Luna Garden Moderator
    #840741

    Hi,

    Please check this extension but seem that it’s not our products. You could hide these Message by go to back-end >> Configuration >> Server >> Error Reporting >> None.

    schemedia Friend
    #841282

    now I feel silly!

    the configuration > server > error reporting was already set to none, so I couldn’t figure why it was displaying errors still.

    when I located the file (you were right… it wasn’t yours after all) there was some hardcoding to turn error reporting on. I removed that and it’s now working.

    sorry to have wasted your time 🙁

    thanks
    robb

    Luna Garden Moderator
    #841581

    Not at all.
    Glad that your problem is solved

Viewing 4 posts - 1 through 4 (of 4 total)

This topic contains 3 replies, has 2 voices, and was last updated by  Luna Garden 8 years, 10 months ago.

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