Welcome to the new R3VLimited Forum
Collapse
X
-
Finally, after a long period of time, I was able to get a DBA who was able to take a glance and clean up a few things, that + a migration over a Linux frontend does show an increase in performance. In regards to the delay, I have no real explanation, but thankfully we should be running a bit better these days.. Happy Holidays!Leave a comment:
-
I now do this by quoting a person, copying the text that inserts in the "reponse", deleting the text that inserts in the "response", quoting the next person, pasting in the previously quoted text, and so on. Basically, I'm using my copy buffer and the response box to build up all the people I want to quote. So it's a bit of a hassle, but I'm not manually writing the "quote" tags anymore.Last edited by mike.bmw; 05-11-2020, 08:37 AM.Leave a comment:
-
Has anybody figured this out? I too can only quote one post at a time.Leave a comment:
-
Dumb question: How do I quote multiple people in the same post? In the past I could click "quote" on a post and then "+" for other posts. Now I can only seem to quote one person per post, unless I manually construct it (via copy/paste and quote syntax).Leave a comment:
-
email notifications not working again - been that way since Sunday.Leave a comment:
-
I have to say again, thanks! The forum feels nice and speedy to use! It's so much easier to edit my DIYs with the speed and added GUI.Leave a comment:
-
-
Thanks, we actually use IIS so its a web.config type process and already have a few in place for forced HTTPS redirect. I thought the cookie issue was fixed on the non www but apparently not so I'll get a redirect in there for it as well.I realized after posting that it's not a record/CNAME issue. The "https://" and/or "www." issue can be resolved easily with an HTTP redirect in the .htaccess file. Force all traffic to the "https://www." version of the site, regardless what they entered into their browser.
Here is an example of the code. It redirects all HTTP to HTTPS and all / to /www.
Code:RewriteEngine on RewriteCond %{HTTPS} off RewriteRule .* https://%{HTTP_HOST}%{REQUEST_URI} [L,R=301] RewriteCond %{HTTP_HOST} !^www\. [NC] RewriteRule .* https://www.%{HTTP_HOST}%{REQUEST_URI} [L,R=301]
This is just an example from a domain I manage. James CrivelloneLeave a comment:
-
-
Yep - Just tried again with three separate photos in different locations.....
"The file you are trying to upload is corrupted."Leave a comment:
-
Yes. Every time I've tried to post photos lately, from any file on my hard drive. Same message as yours.Leave a comment:
-
I realized after posting that it's not a record/CNAME issue. The "https://" and/or "www." issue can be resolved easily with an HTTP redirect in the .htaccess file. Force all traffic to the "https://www." version of the site, regardless what they entered into their browser.
Here is an example of the code. It redirects all HTTP to HTTPS and all / to /www.
Code:RewriteEngine on RewriteCond %{HTTPS} off RewriteRule .* https://%{HTTP_HOST}%{REQUEST_URI} [L,R=301] RewriteCond %{HTTP_HOST} !^www\. [NC] RewriteRule .* https://www.%{HTTP_HOST}%{REQUEST_URI} [L,R=301]
This is just an example from a domain I manage. James Crivellone
Leave a comment:
-
^No. I've been redoing my DIY pictures recently as well as my build thread.
On a speed note, I haven't had any stalls loading pages yesterday after work. It feels quite snappy. Still not NEAR as fast as before the update in 2019, but this is now very usable so far!Leave a comment:
-
Is anyone having issues when trying to post pictures? I keep getting a message saying my file is corrupted. I've tried uploading them from my phone and computer and still get the same result. Any help would be appreciated. Thanks.Leave a comment:

Leave a comment: