Weird Issues after moving website to another webhost
We're running Concrete 184.108.40.206. Here's the issues I've noticed, with the built in form block, the success message no longer appears. The forms work like they should otherwise, but the user doesn't receive the message that pops up above the form saying their message was sent. The URL changes to ?surveySuccess= etc, but no yellow bar loads.
I'm using Contact Directory 1.4 for our directory and it was brought to my attention the other pages don't load. There's 50 results that show, and 4 pages overall, but when you click a page or next, the URL changes to reflect the page number, but it doesn't actually change the page.
Now here's the weird part that I don't understand, those two issues are not an issue when I'm editing the page. When I am logged in and can edit the page, I can fill out the form and get a success message and I can view the other pages of the directory, no problem.
Another weird issue that just might come down to a caching issue, the edit bar will disappear on certain pages, but will reappear when I refresh the web browser. So if the edit bar is missing on a page I'm trying to edit, I click refresh and it's back.
Does anyone have any idea on what could be the issue? If it matters we went from a Linux environment to a Windows environment.
Here's one of the forms you could test.
The directory page
Please let me know if you guys can think of anything, thank you!
I wonder if there's some cache settings that need to be altered for concrete5 to function properly in this Windows environment?
>Another weird issue that just might come down to a caching issue, the edit bar will
>disappear on certain pages, but will reappear when I refresh the web browser. So if the
>edit bar is missing on a page I'm trying to edit, I click refresh and it's back.
That can be symptomatic of page caching in concrete5. The fact that you're able to see the edit bar after you reload is fairly normal. With page caching on, c5 sets a header when it sends the page back to the browser telling the browser that the page will expire at some time in the future. Normal browser behaviour is to honour that setting and not to request the page again until it has expired, or you force it to with a refresh.