Marc

That is correct. They would need to remove that payment method if its incorrect. The reason you cannot edit stored payment methods, is that they are not actually stored within invision, but rather within the payment processor.

There would be no way in which to do that with the platform at present. The bell icon is not actually how many unread items you have under notifications, its how many notifications you have. Once you click therefore, you have see the notifications. The items themselves will remain unread. You can see which have been visited if you click on the list still, as you can see below

That test you mention there is actually history_spam_defense_1 EDIT: Sorry, missed the latter part there. Where is it you are seeing this coming up?

We would need to look further into this for you, however the access details on file appear to be incorrect or missing. Could you please update these details by visiting your client area, selecting the relevant purchase, then clicking "Review/Update Access Information" under the "Stored Access Information" section. We look forward to further assisting you.

Check your htaccess. It looks like you moved your file, but haven't updated it. You can download a new one from your admin CP at System>Search Engine Optimisation if needed

Should add to this, please let us know if you have found a bug within the software, then we can ensure we get it resolved

I'm very sorry to hear you feel that way about our support team. While I fully understand your frustration (Its frustrating to myself when I have an issue I cant resolve), let me explain the situation from a support standpoint, in terms of your own site there. At present you have 19 applications which were not written by our team (3rd party), and 23 plugins. Any one of these could be causing issues on your site in various locations. You mentioned there about troubleshooting, and indeed switching these off for any developer would be the very first course of action in determining the cause of an issue. These 'hook' into 213 locations within our core code, and therefore can very much affect how things work, and cause bugs. We very much wish that wasn't the case ourselves, but unfortunately this is the case if you run modifications to your site. In addition to the above, while looking at your system in an aid to troubleshoot the issue, we would look at anything which may be 'likely' causes. You have many items which are out of date. That not only can lead to issues, but is almost certain to. Many updates are done so in order to resolve bugs, so you are actually running code known to be broken in most cases. We look at system logs, of which you have 11 pages of in 30 days. Usually that would be expected to be empty. We then have cloudflare in the mix. This, in addition to setup issues server side and 3rd party code issues, is one of our highest causes of issues on self hosted platforms. Its only sensible to ask that this is switched off. The above being said, at no point have we stated we will not look into your issue, and at no point have we stated the issue 'is 3rd party'. What we actually asked is that these things are checked first, before we continue with our investigation. There has been no further response on the ticket since that point. To use your own analogy there. It's like you visit a doctor for a headache, the receptionist seeing you have blood running down your head one side, a hole in the other side, you have a hat which looks to be too tight and crushing your skull, and the nurse saying "Before we continue, we need to check the obvious. We need to remove that hat, patch that hole, and check to see where the bleeding is coming from". Unfortunately, that nurse is not going to send you to the doctor before performing her preliminary assessments and checks. We're certainly not here to work against you Guarav, and again, I'm personally sorry to hear you believe we are. It's very much in our interest to ensure your issues is resolved as quickly as possible.

As mentioned, you would require some SSO development in order to achieve this. You would need a 3rd party developer to do this, or we do offer this as a paid service on our creator pro and upward, which you can see on our packages page here https://invisioncommunity.com/buy

If not, I would need to know the member who was logged in at the time and could see the club, and the name of that club

The issue there is that you have commerce installed on a site which doenst have a license for it. Not sure if you have switched your licenses at some point. You need to uninstall that application and start the upgrade again

We wouldnt usually hide topics unless there is a valid reason for this, as we would return with the answer to what was causing the issue for others

As this contains somewhat private information I have moved this

There is no fix there. Its actually working as intended. You should have it set on "Specific time period" and set that. By default its set to 365 days.

That would be if they are unable to access areas, not if they have no permission to upload. i believe that may be what you are missing here.

Please disable all 3rd party item, and then test this again. I am not seeing any errores related to that item, but I am seeing a large amount of errors on your system generally. Also disable cloudflare

Please ensure the htaccess details on file are up to date, as they dont seem to be working at present

You would need to check within your admin CP and check the payment attached to the transaction to see why it failed

No problem at all. Glad you have what you need there

Ok, so you would actually set this to specific time period, and set it to a larger period than you need. By default this is 365 days. You can see it on ours for all time only because we are using elasticsearch. Bear in mind the stream is unread content, so would really be intended for short periods of time anyway. Even 365 days would be quite excessive

You can move topics from the admin CP if you have a criteria in which to move them on. Next to the forum in question in the admin CP, select "Move/delete content" and you will be given the options there

Is that restsharp you are using I assume?

Sorry, "placing" above should read "replacing". For example byte[] png = FileToByteArray("C:\\Users\\UserName\\Desktop\\Capture1.png"); restRequest.AddParameter("fields[276][Test.png]", png); Note I havent tested this myself as of yet. If you still have problems with that, you would need to leave it with me while I have chance to take a look.

So in your case, you would be placing var Mydate = new { SS = FileContent // Convert.ToBase64String(FileContent) }; var Image1 = JsonConvert.SerializeObject(Mydate); var png = JsonConvert.DeserializeObject<JObject>(Image1); With byte[] png = FileToByteArray("C:\\Users\\UserName\\Desktop\\Capture1.png"); and adding the function to your project public byte[] FileToByteArray(string fileName) { byte[] buff = null; FileStream fs = new FileStream(fileName, FileMode.Open, FileAccess.Read); BinaryReader br = new BinaryReader(fs); long numBytes = new FileInfo(fileName).Length; buff = br.ReadBytes((int)numBytes); return buff; }

See if you have any luck with this for getting the byte array for your file byte[] yourFile = FileToByteArray("C:\\Users\\UserName\\Desktop\\Capture1.png"); public byte[] FileToByteArray(string fileName) { byte[] buff = null; FileStream fs = new FileStream(fileName, FileMode.Open, FileAccess.Read); BinaryReader br = new BinaryReader(fs); long numBytes = new FileInfo(fileName).Length; buff = br.ReadBytes((int)numBytes); return buff; }

What is the error that is showing in your system logs relating to that? If not, please leave it with me and will try somehting in .net myself to see whats happening. Which database are you using? I can then download a copy of that database and use that for testing