Jump to content

Jujuwar

Members
  • Posts

    617
  • Joined

  • Last visited

 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 Jujuwar

  1. 10 hours ago, BankFodder said:

    Hi, since our upgrade to 4.4.1, we have been getting lots of problems with this plug-in displaying template errors.

    As soon as the template is disabled, all the errors clear up.

    Clearly there's an incompatibility here. Can you help please?

    Did you apply the update of this app that brings 4.4 compatibility? You should check if app's version is 3.2.0 😉 

  2. On 2/6/2019 at 5:55 PM, Maniutek said:

    Invision Community v4.4.0 Beta 3

    
    
    [[Template core/front/global/prefix is throwing an error. This theme may be out of date. Run the support tool in the AdminCP to restore the default theme.]]

    hm?

    I don't know if you found a temporary fix at this time but for anyone else that may have this problem until a patch is published:

    This is due to a constant that doesn't exists anymore in IPS 4.4 :

    Error: Undefined constant 'IPS\HTMLENTITIES'

    After checking, in the file init.php (v 4.3.6):

    'HTMLENTITIES'						=> ENT_DISALLOWED, // @deprecated and will be removed in 4.4

    The fix:

    Edit the file applications/advancedtagsprefixes/hooks/formatPrefix.php and replace (2 places):

    \IPS\HTMLENTITIES

    by

    ENT_DISALLOWED

    and run the support tools to clear the cache.

  3. On 2017-6-4 at 4:40 PM, Ryan H. said:

    Can't say. Anyone else know? I expect most things will be fine, but tag management section may not (I think they were planning to remove part of the functionality it uses).

    I just tried to manage tags,prefix,... in ACP and it works on 4.2 b4.
    Same on frontend, I didn't see any issue.

  4. 23 minutes ago, krikri89 said:

    hello how i can fix it? 

    thanks 

    You wait for the next update of IPS (4.1.19.1 probably) or you download the first patch (An issue has been identified where certain hooks may stop working on 4.1.19. If you are having problems with some third party plugins or applications, upload this file) mentioned here : https://invisionpower.com/release-notes/4119-r59/ and you apply it via FTP in the same directory mentioned in the link of the patch (system/Theme)

  5. 5 hours ago, motomac said:

    @Ryan H. Rhett Buck, Marc Stridgen and Jim Morrissey have been trying to convince me it's application problem for 2 days. They are sure it's not an IPS problem and don't want to escalate my ticket to the next level.

    What did they say exactly?

    I just tried to update this application on my test site and I don't get any error.
    Did you try to unzip the archive with 7Zip (if you don't already do it with this one)?

  6. Hello,

    I've tried to update my test forum to 4.1.19b3 and it seems that AT&P isn't compatible with this version. Prefix aren't visible, just as mentionned in 

    Furthermore, in support tools, there is database error in relation with the app:

    ALTER TABLE `IPB_forums_forums` CHANGE COLUMN `require_prefix` `require_prefix` TINYINT NULL DEFAULT 0 COMMENT 'AT&P: Require a prefix'
    ALTER TABLE `IPB_forums_forums` CHANGE COLUMN `show_prefix_in_desc` `show_prefix_in_desc` TINYINT NULL DEFAULT 0 COMMENT 'AT&P: Show prefixes on index'
    ALTER TABLE `IPB_forums_topic_mmod` CHANGE COLUMN `topic_prefix` `topic_prefix` INT NULL DEFAULT -1 COMMENT 'AT&P: Topic prefix'

    If needed, I can give an access to my test forum.

  7. On 22/02/2017 at 3:00 AM, Ryan H. said:

    Following up on this: IPS asked for someone affected (like you) to open a support ticket explaining the issue. Could you do that?

    Reference this topic and post: https://invisionpower.com/forums/topic/435839-ipshelperstabledb-group-by-paginator-issue/?do=findComment&comment=2678988

    Quote

    Hi Julien,

    We are actually going to be deprecating the use of GROUP BY within the Table Db helper - unfortunately, it creates further issues in MySQL 5.7.

    https://invisionpower.com/forums/topic/434359-deprecated-notices-for-42/

    Regards,
    Ryan Ashbrook - Development
    Invision Power Services, Inc.

     

  8. 2 hours ago, Unlucky said:

    Is there a setting to stop the prefix showing in the page title

    Can this have an adverse effect on SEO? We have been told it does.

    For example https://www.walkingfootball.com/chat/topic/119-klb-walking-football/

    Google will see this page title as [fitness session] KLB Walking Football

    Where as we want google to see it just as KLB Walking Football

    We use http://www.spyfu.com/ to do all our keyword / keyphrase analysis and name pages for seo purposes when we want to target a particular keyphrase.

    We are worried that the prefix in brackets is bad for this from what we have been told.

    We of course still want to use the prefix for topics - we just don't want it in the page title itself.

    So is there a way around this without manually editing every single page ourselves using the invision Live Meta Tag Editor

    thanks

    In the ACP > Community > Advanced Tags > Settings : disable "Add topic prefix to the page title"

  9. 10 hours ago, Ryan H. said:

    :mellow: Awesome. I can't imagine how.

    I take a look at that and the difference is that when  Advanced Tags & Prefixes is enabled the <span> of prefix contains the template Core > Global > Prefix 

    {{if $text}}
    	<a href="{url="app=core&module=search&controller=search&tags={$encoded}" seoTemplate="tags"}" title="{lang="find_tagged_content" sprintf="$text"}" class='ipsTag_prefix'><span>{$text}</span></a>
    {{endif}}

    This template was update in .17, to add the condition {{if $text}}

    And when I disable the app, the span doesn't contains this link.

    This template is called in Forums > Topics > Topic at line 70

    {{if $topic->prefix() OR ( $topic->canEdit() AND $topic::canTag( NULL, $topic->container() ) AND $topic::canPrefix( NULL, $topic->container() ) )}}
    	<span {{if !$topic->prefix()}}class='ipsHide'{{endif}} {{if ( $topic->canEdit() AND $topic::canTag( NULL, $topic->container() ) AND $topic::canPrefix( NULL, $topic->container() ) )}}data-editablePrefix{{endif}}>
      		{template="prefix" group="global" app="core" params="$topic->prefix( TRUE ), $topic->prefix()"}
    	</span>
    {{endif}}

    In the prefix template, $text is the second parameter :p 

    Hope this will help you!

     

  10. On 09/11/2016 at 5:10 AM, Ryan H. said:

    I spent a while exploring it. Found the source of the error, but not a solution that doesn't break AT&P in the process. There's some really bizarre behavior going on with the IPS core here. I reached out to someone about it.

    Any news about this?

×
×
  • Create New...