Ryan H.

  • Content count

  • Joined

  • Last visited

About Ryan H.

  • Rank
    Watch how I soar.
  • Birthday June 21

IPS Marketplace

  • Resources Contributor
    Total file submissions: 16

Recent Profile Visitors

56,658 profile views
  1. I don't do release tests, but assume yes unless anyone indicates otherwise.
  2. Okay. Can you PM me ACP and FTP access to investigate? I don't have Pages to see it myself. Please send any creds via https://privnote.com for security.
  3. They're slightly mistaken, in that I never changed anything. My impression is it broke in one IPS update, and got fixed in another. If it's broken again, what IPS version are you running?
  4. Were you able to get it worked out, or do you still need help?
  5. There's a section in advanced settings in the ACP to change FURL templates. That's what my explanation was referring to. I don't have an ACP handy to tell you exactly where that is -- but if you point IPS toward this and my message above, they should be able to help.
  6. If you're not comfortable applying the fix, you can just wait until the next release. It'll be fixed then. In the mean time, ignore those three errors. Nothing is actually wrong with your site, and nothing is broken because of them. The only problem is with the support tool database checker seeing things as incorrect when they aren't.
  7. Good call. Thanks for sharing!
  8. Thanks. Your site should be patched now. For anyone else, you can pretty much just change the pages/{@page} FURL template to pages/p-{@page} (or any other static text in the second part) to work around the issue. That will mean all of your page URLs change, though; for the moment, that's unavoidable.
  9. The part where I do respond and then don't hear a thing for half a week isn't helping to resolve this quickly either.
  10. Yes, in my application code. No, it would not be overwritten by updating IPS. Look, I don't know what to say to you. I've told you repeatedly that you need to have some patience (again, I cannot respond to everything in a matter of hours); I've explained the situation and how this issue is largely out of my control right now; and I asked for access to your site to work around the issue for you four days ago. You have yet to provide that access, so I am not sure how you expect me to do anything.
  11. It will require a number of code changes.
  12. Oh, my mistake. If you can PM me FTP access, I should be able to sort it out for you then. It won't be ideal, but it'll work. I never said it won't be fixed, just that my options right now are extremely limited. I can't control IPS's decisions or priorities.
  13. Yes. You're welcome to follow the bug report yourself. As it stands, I don't think it's something I can solve outside of some response to that report. There's no telling how long that might take (days, months). I could give you an alternate FURL configuration for the app to work around it, but I think you're on IPS Cloud so I'm not sure that would help anyway.
  14. I'll include it in the next update. I don't intend to release a new version for one file for something that isn't broken except for when you try to run the support diagnostic. If it bothers you, the file as Gabriel/IPS so helpfully provided will fix it.
  15. Getting a bit off-topic, but I appreciate the perspective. In general, I would always advocate running a development/test copy of production, where you try any upgrades and changes before doing it live. That should help catch issues before they become much bigger issues. Routine backups are a good idea regardless. That being said: I feel your pain. Lack of backwards-compatibility is definitely a big issue (my other app was plagued by it for a while, in one case they tweaked a feature three different ways in three consecutive releases), and contributor rants on the subject are long and numerous. There's not much to be done about it. IPS insists on being able to refactor and fix framework bugs as deemed necessary, at any time. To their credit, they have made an effort to try maintaining BC, post about breaking changes in advance, and make pre-release builds available. That's an improvement over what it was. Still, always unintended side-effects (see: this). I understand their perspective, and they do what they have to do for their own business interests. Telling people, 'hey, we won't be able to fix this bug until the next major release in a year or two because it might break other stuff' isn't an option as far as they're concerned. The flip side, of course, is that they've created an ecosystem with little semblance of stability. It's cumbersome to maintain anything substantial on it, and I think the number and state of contributors around is demonstrative. It may be there are different design decisions they could've made to alleviate these issues--a more rigid and compact core, or a formal API and semantic versioning, or TDD, or using a common framework like Symfony... but that's largely immaterial. Not the reality we live in. As for me, I try to fix my stuff when it breaks, but I've moved on to other pastures.