DemonGoddess

Nope, it has to do with Chrome being more forgiving of programming errors in many for instances. Although Chrome can get right testy about big boo-boos, minor stuff, it ignores. This was ONE sentence in one of the linked files, so Chrome ignored the redirect loop. It went by the master files, not the the subordinate file.

Don't feel bad. I appreciate your thanks!

Nope, was actually a bad redirect in an unexpected file. As the database works with scripts to be relational, ONE bad command in a linked file will screw it all up. It should be working now in all browser. The search function for members from your profile is currently not quite right, not sure what's going on there yet. We're working on it, too. BUT, to search a member from within any given archive does work. So that means there is more stuff that has to be done yet, but manta is already aware of the issues with the new code deprecation as well. The IMPORTANT thing was to get the site loading again, stop the time outs, and make it so the archive was once again accessible, which it was not. The last BIG software upgrade is the forum itself. As this is a major, from one version to the next, and up a couple versions in language for scripts and database, we pay for licensing and assistance, so IPS will do this one FOR me. I'm capable of doing it myself, but I'm more comfortable with THEM doing it, because they have snippets available that I would not.

Edge is working. I refuse to use Firefux anymore ('tis a resource piggy). The oddball redirect issue is fixed. Was in a file that was not obvious for it to be in.

Thank you! Manta and I appreciate this. The patch is done for the oddball redirect. The upgrade is something that we've been doing for a few years, a bit at a time. The code was originally Storyline, which is defunct. I've, over the years, looked at many other packages, hoping we wouldn't have to go from scratch with this. After much trying and hair pulling because it wasn't working (my own server, offsite), we determined the best way to go, to KEEP the data, was to rewrite it all. That's something manta does, primarily. There is one last phase to do, and that part will cost the site $750.00USD. However, we were running in to glitches, which led to the server upgrade in the FIRST place. As we both work, and have heavy real life obligations, at times, what either of us can do slows down significantly. Simply BECAUSE of our real life obligations. I can do plenty on my own, but I can tell you for certain, without manta, none of this would work. This is why she's the primary, and I merely help on the coding end. MY thing is databases, so it's a good partnership.

USE CHROME!!!!!

Okay. Let me be real clear on this. Until I fix the deprecated command in every fecking php file in the archive, use Chrome exclusively. Chrome is not having this issue. I CANNOT do this at work. I work during the day. My days vary. I usually get home about 4:30. Today I got home a little earlier. So, I will be getting on this very shortly. I've heard from Nexcess, it isn't the Apache setting. It's DEFINITELY the deprecated command. By the way, this is the command that tells php that the file IS php. Hence the having to go through every file and adding three letters to it.

Did you not READ anything??? I just now got home from WORK. I WORK during the day. This means I can't do anything at all with this. I said this morning I would take care of all this AFTER WORK.

For now, until I get confirmation on an Apache setting from the hosting company, and also until I manually go through each file and correct one last deprecated command, use Chrome. You won't have those issues.

Edge isn't slow loading for me, but I was able to duplicate the not clicking in to a story thing, and being redirected to the latest listing instead. There are two things that need to be checked. One has to be checked by the hosting company, as they have access to the Apache settings on the server, and we do not. The other is to see if there is one other deprecated function. -- on edit --- okay, the deprecated function is definitely an issue, it appears. I'll have to fix this after work though. In the meantime, until I get home, and go through all the scripts and make this correction, use Chrome.

When you do clear cache and cookies, you must close and restart the browser in question. "The page isn't redirecting properly" is a COOKIE error, so please clear the cookies too.

IE is end of life. That's why Microsoft released Edge, because IE has many, many issues they're not interested in fixing. Having said that, this page has detailed instructions on how to do this for IE. Personally, I'd ditch the browser and go with Chrome. But, I've been saying THAT for years.

what browser are you using? cache is not the same as browser history. What you can do also is try a forced refresh which will also clear the cache for the page you're trying to reach. To do that, hold down ctrl, and then press F5

clear your cache, because the story links work fine

hp goes to hp. I just checked

Nope, the archive are accessible. I did say to give us about 10 to 15 minutes ya know, to fix the redirect issue.

give us another 5 to 10 minutes, there was a path mix up which is being corrected as I type this.

There shouldn't be any more. I expect you tried going in to a subdomain where the patch had not yet been applied. As to the adult++ issue, I need to know the subdomain so I can fix it

Manta finished it up, and found all kinds of nasty little things which needed squished. I knew she would Thank you manta2g!!!! thank you! Last big upgrade is currently in queue with IPS, and that is for this forum.

I counted it, and yes, you have 290 total characters for the summary. HOWEVER, last I checked, the field itself was limited. Having said that, this was a number of years ago. Could be that the main tech actually changed the properties of the field as well. Won't know until I look.

The field itself is set to have 240 characters allowed.

the field actually truncates if you exceed the maxlength. So, sure, you can edit it, but if you exceed it, it won't save all your changes.

I have some files which SHOULD be fixed, which I'll upload after work. I'm not doing it now, because I want to be at my computer to observe what changes, if any, occur. Aside from that, being at my computer with the files, I can easily change them BACK, if the changes make things worse. I get home after 4 pm EST. Thank you for your continued patience.

You've not read the updates about the server upgrade then, apparently. That answers any questions you may have about it.