Jump to content

Randy Calvert

Clients
  • Posts

    3,945
  • Joined

  • Last visited

  • Days Won

    78

 Content Type 

Downloads

Release Notes

IPS4 Guides

IPS4 Developer Documentation

Invision Community Blog

Development Blog

Deprecation Tracker

Providers Directory

Projects

Release Notes v5

Invision Community 5 Bug Tracker

Forums

Events

Store

Gallery

Everything posted by Randy Calvert

  1. ACP > System > Site Features > Integrations Find Matomo and choose "Enable" and paste your code.
  2. See #2 in my reply to your other topic on this issue:
  3. Turn off WAF for the api folder or whatever folder is being called by Zapier.
  4. By any chance are you using Redis? If you are, I've seem some issues where some settings seem to be pulled from that shared instance instead of it's local settings. (I installed a copy of an instance to a new AWS instance to make it a dev setup, but it was communicating with my prod instance because it was using the same Redis details.) On the test install, don't use Redis and see if that fixes your problem.
  5. ACP > System > Settings > Posting What is your edit log set to? If you're not logging edits or only logging that an edit was made, you wont be able to restore the content as it was not tracked. If you are logging edits AND what was changed, you'll see below an edited post something like the following at the bottom of the edited post: You would click on "see edit history" and you could see all of the changes. They're listed most recent first. Copy/paste the content you want and paste it into the edit screen of the post to restore it.
  6. By the way... per @Matt: This was noted in:
  7. This is not supported. This requires a LOT of backend code changes within IPS to support. The editor is used in virtually EVERY single component of the site. You can't just rip it out and drop in a new version.
  8. If you were upgrading your IPB version... you most likely were upgrading to the latest version. #1 - The new version requires at least PHP8. Are you running PHP8 or PHP8.1? (If not, you need to be to run the latest version.) #2 - If you meet all of the system requirements, including the PHP version... you most likely have a 3rd party resource that is causing problems. You can try using recovery mode to disable everything and let you try to login with everything turned off. You can then turn on resources one by one to figure out your problem child. When you use recovery mode... you set the specific variable in your constants.php file. (If you don't have one, you create one.) Then login to the ACP... you'll get a message saying everything is being disabled. Once done, you'll need to remove the recovery variable (or delete the constants file if that was all that was in it.) From there hopefully you'll be able to login to your ACPa again.
  9. It basically looks on the last message in the conversation and says has it been more than X days since the last new one was posted. So if it was never replied to, it would use the start date since it was the date of the last message in the conversation.
  10. In that case, you would want option 2 in that list. Edit the baseurl to point to a different (hopefully working) repository. 🙂 Also MariaDB may be already in one of those other channels you subscribe to. You might want to confirm that before spending time on adding different repos. If it is, just remove the bad repo and call it a day. If not, find an alternative and add it and disable the bad one.
  11. That setting is for PMs (called Conversations).
  12. The release notes for the upcoming release are already posted: https://invisioncommunity.com/release-notes/ Click on 4.7.5 beta 1. So again… it’s unlikely to make it this year if it is done at all in core.
  13. By having them host the DNS, they can serve both www.domain.com and domain.com. (This is called the apex.) Because they use AWS’s Cloudfront, they have to control DNS to point domain.com to www.domain.com. (They don’t use a single fixed IP address so it’s how they solve having multiple addresses for the apex.)
  14. Nope. For anyone who had not recently been to the site, they pickup the change almost as soon as you submit it. For those who have recently visited, it’s typically cached a few hours. (Lower your TTL in your domain dns settings to reduce that time to something like 500 seconds.) As a hint… if you’re having them host your DNS… give them all of your existing DNS records ahead of time like your MX record for mail etc.
  15. Yes… Marc started the import first thing in the morning UK time, which is around 5 hours past Eastern time. I had an email at 5:04am saying the migration was done. I was checking the site starting at 6:45 and fixing minor issues on the temporary URL. By 7:10am, I had given the OK to switch the temporary address to the permanent one. It took about an hour to figure out why it was failing (I had a prior AWS Cloudfront distribution associated with my domain) which was preventing IPS from creating one. Had I not had that issue, it could have been up much faster. I technically could have been online faster also but I was not up till around 6:30 to check on progress. Olivia and Marc have migrations down to a science. They do good work. 🙂
  16. Using phpMyAdmin, run an optimize on that table. The bigger question for your host however is why it’s not cleaning up after itself in the first place.
  17. What I did was took the site offline at 1am Eastern. I provided a backup of the database and all site files. Marc did the import first thing in the morning UK time so I was up and running by 8am. That included taking time to solve a few bugs related to third party plugins and that I had an old Cloudfront distribution that was preventing IPS from creating the same one on their side. It would have been done an hour or so earlier outside of those issues. While you could technically turn the site back on read only… you would lose anything that happens since that export. For example, private messages… topic view counters, and as noted earlier password resets etc. I simply used the offline board as a way of knowing the DNS change took effect. By having the old board offline, once people saw the site back they knew the maintenance was complete.
  18. The MariaDB repo you're trying to call is not responding. In looking at the URL (http://yum.mariadb.org/10.2/centos7-amd64/repodata/repomd.xml), it shows up as a 404 error. So yes... it indeed does look to be a bad repo. The output above actually gives you your available options... you can permanently disable that repo by running: yum-config-manager --disable mariadb
  19. There is nothing announced regarding this. IPS has already said there is not going to be any new features in the December release. It's only going to be bug fixes. I would suggest watching the release notes for each new version to see if anything is added.
  20. You would need to look at your server error logs to see what is happening there. The fact that a reboot fixes the problem indicates it's a problem with your server configuration rather than the software itself. It's possible the server is running out of memory which causes the web server processes to get hung/fail. Without knowing exactly what is going on with the server, it's impossible to say... but if rebooting fixes the problem, it's about a 90% chance it's a server problem and not a software problem.
  21. No, but I made an effort to confirm each of my 3rd party resources first.
  22. @Gary I believe when attempting to reset the license, the system would detect the production URL still valid and block the reset. (I can’t speak for the OP, but that was my observation when I did it myself awhile back. It required intervention by the staff to reset.)
  23. The forums here are the way to contact support. Someone from the IPS team will respond soon. 🙂
  24. It looks like a 500 error is being triggered there. You might want to review your Apache error logs to see what is happening there if n more detail. My guess off hand is it’s mod_security or something similar blocking it.
  25. It occasionally happens if there were certain other things happening like a service worker prompt. Just reload the page and it works again.
×
×
  • Create New...