Jump to content

Jim M

Invision Community Team
  • Posts

    8,412
  • Joined

  • Last visited

  • Days Won

    39

 Content Type 

Downloads

Release Notes

IPS4 Guides

IPS4 Developer Documentation

Invision Community Blog

Development Blog

Deprecation Tracker

Providers Directory

Forums

Events

Store

Gallery

Everything posted by Jim M

  1. The queries are 100% correct. The issue is your database server, which is why we are asking you to perform this with your hosting provider.
  2. You would need to have them execute those commands on your database and see what happens. Explain to them that when the software does it, the database encounters problems.
  3. Thanks! I've moved this to a ticket so we can further investigate and see what is happening here.
  4. Are you OK with us adding to the article?
  5. I would advise checking that with your hosting provider because something is happening when that executes. It is best for your hosting provider to review what is happening.
  6. So the article body there is just over 67k characters. The article is quite large but nothing which the dataset can't handle so far. What is the total size of the article which you are attempting to add? How many more images are you attempting to add? You may hit some restriction on our firewall prior to hitting the size allotment for the database.
  7. Do you have an example of what you're attempting to post? I think it would be rather hard to hit a limit there but there may be something else going on.
  8. Sounds like a temporary block but please let us know if it happens permanently again 🙂
  9. The "file" is what you are seeing there in your screenshot. "custom.css" is the custom.css file. These are all "virtual" files as it really is just stored in a database but I used the word "file" to simply relate it to a regular instance most people are familiar with. Both themes you named these as "custom.css" (or used the default provided CSS file). This is why your CSS is overwriting as it is intended. You would want to create a new CSS file (scroll down to the bottom -> click new -> CSS File). Then name it something you'd recognize when in the child theme, I suggested "parent" to be in the parent theme and "child" to be in the child so you understand. There is no need to include the CSS. Theme's CSS are automatically included on all pages.
  10. The software itself, does indeed prevent conflicts. The database configuration, however, is where that falls short. Improvements can indeed be made; we both agree on this. However, in the current state of things, if third party applications/plugins currently don't implement the same validations or prevent/break those from happening, that can create issues that users are seeing. Regardless of what we do, third party providers would still need to resolve their solution or errors would still happen, they won't create conflicts, but they'd still happen. If you want to see improvements that you mention here, please provide them in the Feedback forum as instructed.
  11. Are you using the URL which you have on file here? If so, I get "No applications to upgrade"
  12. It would have been in the red box on the page mentioned 🙂 . Could have just been at the right time. Unsure if you didn't see it honestly as it would have been displayed to anyone there.
  13. Going to the upgrader now, I am seeing the below: The error reported was: session_start(): Failed to read session data: files (path: /var/opt/remi/php81/lib/php/session) You will want to check your PHP session configuration as it cannot read/write to the location there. You will want to ensure it exists.
  14. Did you recently upgrade PHP as a part of this process prior to running into the error? It could be that PHP sessions are indeed not configured properly for that part of the error. You would want to check the directory which they are stored and ensure that it exists and is writable. If that all checks out, I would confirm what Marc stated about crashed tables.
  15. This would likely be coming from your PHP or SMTP configuration. We do not set anything outside of what you see there for email sending.
  16. I would advise contacting your hosting provider then to see what is happening on the server. Ultimately, I would think that something is happening on the server to have this happen. If they are unsure, you can also do another restore of your database and simplify your environment. Disable any third party applications/plugins, integrations, APIs, etc... Only have the core software touching your database.
  17. Sorry, let me rephrase what I meant. After you did the restore, did you run that again and that is when the data disappeared again?
  18. Does the data disappear when you run the fix on that?
  19. You're more than welcome to make this suggestion, as mentioned in my comment above. Please do so in the Feedback forum so it does not get lost. While I get what you're saying that there could be room for improvement (what software doesn't?). If there was a core only issue, we would definitely be seeing a lot more of this. The fact that we aren't, may be specific to any number of factors. We need an example that doesn't go away when we remove third party influences to completely determine the issue. To make the analogy more realistic, it is akin to Ford allowing customers to choose a VIN via a software. The software doesn't allow conflicts. Then an aftermarket source then allows changes to that VIN, which then creates conflicts.
  20. When you create a Child theme, the Parent theme's CSS files will now be in the child. This means that if you make any modifications to the Child's theme CSS files, you could be removing the parent theme's CSS. You may wish to create a CSS file called "parent" in your Parent theme and "child" in your Child theme. You can then use CSS as you are wanting to here. In the example above, the white color is in my parent theme CSS file and the black color is in my child theme CSS file. I am able to use cascading just fine 😉
  21. This is still an open issue. I'm afraid, we cannot provide an ETA of the resolution to this at this time.
  22. Thank you for bringing this issue to our attention! I can confirm this should be further reviewed and I have logged an internal bug report for our development team to investigate and address as necessary, in a future maintenance release.
×
×
  • Create New...