Marc
-
Posts
15,921 -
Joined
-
Last visited
-
Days Won
277
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 Marc
-
I think you will find the same with the others.
-
Are all your tables INNODB and have the row type set to dynamic?
-
This appears still to be active -
Of your database is that large with only a very small number of posts, then something is very likely wrong on the hosting side, to be honest. However you do have a duplicate set of data there. check your prefix in conf_global.php. If it doesnt start with orig_ then you should delete all the tables that begin with that. Ensure you backup of course
-
Could you clarify, are they still getting it now? This is something we implemented, in answer to your question. But it should be very very rare anyone sees it. Most people wouldnt ever see it
-
There are bits we havent spoken about as of yet, as Matt mentioned in terms of donations for example. We will get to them at some point 🙂
-
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.
-
Please could you disable 2 factor temporarily, or set up questions for this and add to your account?
-
In terms of this, it is something that shouldnt really be coming up. It was added as a 'just in case', but really your users shouldnt be seeing it unless they are doing something very odd. So it would be a case of us having a look at the rules to prevent the issue, rather than prettifying the problem, so to speak
-
I can bring up that internally. Just ensuring the issue of of it showing all the time is resolved first of all.
-
No, its not the look of it. Its more the fact its present. You really shouldnt see it very often at all. Most of your users probably wouldnt ever see it
-
This has been responded to here
-
Problem with Google Authenticator
Marc replied to Safety1st's topic in Classic self-hosted technical help
You mentioned above you are using cisco connect -
Please check this again now. We have made some changed. Any issues, please let us know
-
Please check this again now. We have made some changed. Any issues, please let us know
-
We are of course constantly working to improve items on our cloud network. The issue being experienced here, is unfortunately the result of an attack on the network which we are actively fine tuning to mitigate. At point point we were blocking 80 million requests, to put in context of the level we have been dealing with.
-
We are aware of an issue there, and this has been reported internally.
-
Please have a read of the following, which shows what this is and why it is important We have however reported internally that people are being shown repeatedly
-
Using same db for both livev forumn and dev forum
Marc replied to georgebkk's topic in General Questions
The short answer to the first question is "It will break". Dont do it. If you connect both to the same database, its simply not a developer forum, as anything you amend/change will affect both instances. You could end up with files being saved to one location, when they should be saved to another, anything cached on disk will be saved to 2 different locations. And these are just the things I can think of from the top of my head. -
ACP: Location map for member shows error
Marc replied to georgebkk's topic in Classic self-hosted technical help
Please could you check to see if you have any errors showing in console? -
An error occurred (500 Error) "No Permission"
Marc replied to AverageJoe23's topic in Classic self-hosted technical help
Glad to hear you got the issue resolved -
I would need to know who the member is too
-
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.
-
But there was more than one! 😄 jk. Reported it as a bug internally for you
-
The intention of a patch is that it is shown only in the support area, which is where you should go if there is an issue on your site. Anything outside of what is a patch would tend to be a release, which indeed you are notified of. Not everyone will need the patch, and we dont want to alert everyone for that reason.
