Ryan H.

  • Content count

  • Joined

  • Last visited

  • Days Won


Ryan H. last won the day on October 15 2015

Ryan H. had the most liked content!

About Ryan H.

  • Rank
    Watch how I soar.
  • Birthday June 21

IPS Marketplace

  • Resources Contributor
    Total file submissions: 16

Recent Profile Visitors

57,404 profile views
  1. 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
  2. I'm not sure what you mean. You can enable or disable tags/prefixes per-board, and you can also explicitly define the specific tags/prefixes allowed to be used in a given board. (For prefixes, it's required.)
  3. It's a bug with IPS relating to how the data is loaded. Unfortunately, there's nothing I can do about it. The only thing wrong is the page count. Yes. Tags and prefixes are core IPS functionality (minus the added permissions, styling, etc. provided by the app). Tags will still be there even if the app is disabled or removed.
  4. Someone reported the same a couple weeks ago, but I never got any further info. https://invisionpower.com/forums/topic/416840-advanced-tags-prefixes-ips-4x/?do=findComment&comment=2673701 What versions of IPB and AT&P? What filters or actions are you applying? Does anything show up if you go all the way into viewing one of the affected topics?
  5. It's a known issue. I have not been able to isolate the root cause of the problem or find a solution that doesn't break my app in the process. I reached out to someone at IPS (a long while ago) but that never got anywhere. At this point, it's not moving anywhere. All I can suggest is temporarily disabling the app while you need to change DB settings.
  6. You can control permissions for prefixes globally or on a per-prefix basis (by member group). You can control permissions for tagging globally, but not on a per-tag basis.
  7. I understand the frustration. I'm frustrated too that something that worked perfectly for two years in IPS now not only doesn't work, but has no practical alternative way of being done. I contacted IPS about it and was told I'm on my own. If this were a bug that's easily and properly fixed, I would have done it when the issue was first raised.
  8. I missed that, sorry. It changes only Easy Pages page URLs. I don't have an install immediately accessible to point you toward that section. You could try searching for 'furl'.
  9. Running five at a time? What filters/actions are you applying? I'll consider it.
  10. This probably isn't sufficient grounds for a refund, but you're welcome to take that up with IPS. They're out of my control. marketplace@invisionpower.com An alternative approach would be to create blocks for your pages' header and footer, and then add those blocks above and below each page you create. You could put any content or HTML you want in those blocks, including those starting and ending tags. Either way, this app is about giving you the power and flexibility to do whatever you want -- that doesn't necessarily mean it'll be easy. Your specific issue seems like more a result of your theme to me, but I'm not going to argue the point.
  11. No, you'll have to add it each time.
  12. I'm sorry, I don't understand what you are asking. You can make pages look any way you want, but you'll have to use the appropriate HTML/CSS/classes to do so. You can use the forum wrapper or not, based on the page settings.
  13. Yes. Thanks, I will look into that further down the line. I shouldn't have been so dismissive. What do you mean by edit a prefix? ACP > Manage Prefixes, and change the title? That won't update any corresponding tags/prefixes actually assigned to content. If that's so, you can change those tags/prefixes in the Manage Tags section.
  14. I don't have any fix beyond what I already explained. If you upgrade again, you'll just need to modify the easypages FURL templates as I described. For that explanation, see this and the two posts following it. If you have any questions or confusion, ask.
  15. ... mysql 5.7 (or your configuration thereof) sucks. Guess that serves me right for trying to fix an issue I can't actually test.