Jump to content

media

Clients
  • Posts

    3,241
  • Joined

  • Last visited

  • Days Won

    3

 Content Type 

Downloads

Release Notes

IPS4 Guides

IPS4 Developer Documentation

Invision Community Blog

Development Blog

Deprecation Tracker

Providers Directory

Forums

Events

Store

Gallery

Posts posted by media

  1. [[Template forums/front/index/forumRow is throwing an error. This theme may be out of date. Run the support tool in the AdminCP to restore the default theme.]]

    After I ran the patch today i got above error message but Template forums/front/index/forumRow it already default version no difference to revert it...

    Got this right after the patch on my system error

    TypeError: round(): Argument #1 ($num) must be of type int|float, string given in /home/media/public_html/forum/system/Lang/Lang.php:935
    Stack trace:
    #0 /home/media/public_html/forum/system/Lang/Lang.php(935): round('68298+', -2)
    #1 /home/media/public_html/forum/system/Theme/Theme.php(885) : eval()'d code(1423): IPS\_Lang->formatNumberShort('68298+')
    #2 /home/media/public_html/forum/system/Theme/SandboxedTemplate.php(61): IPS\Theme\class_forums_front_index->forumRow(Object(IPS\forums\Forum))
    #3 /home/media/public_html/forum/system/Theme/Theme.php(885) : eval()'d code(1920): IPS\Theme\_SandboxedTemplate->__call('forumRow', Array)
    #4 /home/media/public_html/forum/system/Theme/SandboxedTemplate.php(61): IPS\Theme\class_forums_front_index->index()
    #5 /home/media/public_html/forum/applications/forums/modules/front/forums/index.php(225): IPS\Theme\_SandboxedTemplate->__call('index', Array)
    #6 /home/media/public_html/forum/system/Dispatcher/Controller.php(118): IPS\forums\modules\front\forums\_index->manage()
    #7 /home/media/public_html/forum/applications/forums/modules/front/forums/index.php(52): IPS\Dispatcher\_Controller->execute()
    #8 /home/media/public_html/forum/system/Dispatcher/Dispatcher.php(153): IPS\forums\modules\front\forums\_index->execute()
    #9 /home/media/public_html/forum/index.php(13): IPS\_Dispatcher->run()
    #10 {main}

     

    #0 /home/media/public_html/forum/system/Theme/SandboxedTemplate.php(71): IPS\_Log::log(Object(TypeError), 'template_error')
    #1 /home/media/public_html/forum/system/Theme/Theme.php(885) : eval()'d code(1920): IPS\Theme\_SandboxedTemplate->__call('forumRow', Array)
    #2 /home/media/public_html/forum/system/Theme/SandboxedTemplate.php(61): IPS\Theme\class_forums_front_index->index()
    #3 /home/media/public_html/forum/applications/forums/modules/front/forums/index.php(225): IPS\Theme\_SandboxedTemplate->__call('index', Array)
    #4 /home/media/public_html/forum/system/Dispatcher/Controller.php(118): IPS\forums\modules\front\forums\_index->manage()
    #5 /home/media/public_html/forum/applications/forums/modules/front/forums/index.php(52): IPS\Dispatcher\_Controller->execute()
    #6 /home/media/public_html/forum/system/Dispatcher/Dispatcher.php(153): IPS\forums\modules\front\forums\_index->execute()
    #7 /home/media/public_html/forum/index.php(13): IPS\_Dispatcher->run()
    #8 {main}

     

    This all happen after applying the patch was available today...

  2. 17 minutes ago, teraßyte said:

    Yes, IPS added a new parameter to a function. It's a simple change if you know how to do it.

    If you need help let me know.

    This is the line that I got from my video app

    Application	Videos System	Mismatching parameter list 	\IPS\videos\Category::setLastComment()	N/A	/applications/videos/sources/Category/Category.php:552	/system/Node/Model.php:1056

    category.php

    line 552 to 555

    Quote

        public function setLastComment( \IPS\Content\Comment $comment=NULL )
        {
            $this->setLastVideo();
        }

     

  3. After latest upgrade invision locked my video app, this happened before but happened after this upgrade too... According to app owner it is compatible 

    Quote

    PHP8 Incompatible Customizations

    We are currently in the process of migrating our platform from PHP7 to PHP8 in order to provide you with the greatest level of performance and security. We've identified one or more Applications or Plugins currently installed on your site which contain PHP8 incompatible hooks and/or subclasses. In PHP8, altering overloaded method signatures within a subclass results in a fatal error which can make a site completely inoperable. Also, our hook system relies on subclasses so this change applies to hooks as well. Therefore, this code must be either replaced with an updated version, removed, or disabled from your site as soon as possible.

    If you are not sure what this means, you must contact the Author of any listed Application or Plugin for an updated version. If you cannot update to a PHP8 compatible version, the Application or Plugin will have to be disabled or removed.

     

  4. 9 minutes ago, Marc Stridgen said:

    I have tagged our developers just to make sure, however as mentioned above, this appears to be twitters end being a bug, more than anything else. If that is the case, its not something we would be able to fix

    No worries, Marc, 

    I truly understand you... Just wanted to make sure we do not miss a code change that's all...

    Thanks

  5. 15 minutes ago, Joey_M said:

    This is something you absolutely must take on the chin, and whilst I understand your point - it is not always possible to provide visible updates to everyone and nor will everyone read them. There are updates on Michael John's site, albeit a bit old, but I don't believe he's someone who would just walk without trying to address things.

    If you managed to get your money's worth from the app, then that's at least one good thing. I would definitely recommend purchasing Adriano's app.

    Yet anything in the real world can and will happen, it's not always as simple as leaving updates and as you mention. Devs won't simply give their resources away for free; it takes a dev to pick them up and to pay a fee for them. In most cases, I think it's more common to see a new resource created from scratch.

    Keep in mind that some Dev's have died, others have left in bad ways, but Michael is between this as far as I can tell. Whatever has his focus must be very important to him. 

     I get what you are saying, but it's not something to be expected.

    It's a gamble on our part; you pay for the resource as it stands and Michael is one of those devs who add features to improve his work without additional fees. Whilst an explanation to say "I am unable to provide updates for the foreseeable future." would be nice.

    There are no guaranteed expectations.

    I don't think we as clients have that right either, at least not to demand it. As I say, I get the frustration, but I sway more towards concern than outrage.

    I totally understand the situation, and I put myself on developers' shoes. 

    Only one thing we want from developers; please let us know if you are exiting (Do not just disappear) 

    And please please give us an exit plan....

    That's all we want... 

    Thank you for your input...

×
×
  • Create New...