Guys - everything worked fine 20/1/15 - two days ago. Perfect in fact. This morning, I'm having someone test the system for me, they click on submit on the form and get a blank page. I've got maximum logging on and see nothing. The server hasn't had any updates as this is manual.
I went into the frontend chronoconnectivity listing, clicked on the pagination button and get a blank screen. Again, no errors.
Very, very strange and terrible timing. Again, no php updates etc. The server configuration hasn't changed.
mark
I went into the frontend chronoconnectivity listing, clicked on the pagination button and get a blank screen. Again, no errors.
Very, very strange and terrible timing. Again, no php updates etc. The server configuration hasn't changed.
mark
Weird. The server is set to be accessed via https on port 3443 - when I view the source of the pagination links, the link presented is https://mydomain.com:3443:3443/index.php?option=com_chronoconnectivity5&view=connection&Itemid=132&page=2"
So the port is in there twice. Remove the second port and the link is fine. Could this be because the installation is migrated from a verified installation on a test site and hasn't been verified with you guys yet? It was working fine Tuesday - if this was the case, I would have expected it to not work then too?
mark
So the port is in there twice. Remove the second port and the link is fine. Could this be because the installation is migrated from a verified installation on a test site and hasn't been verified with you guys yet? It was working fine Tuesday - if this was the case, I would have expected it to not work then too?
mark
OK! Setting relative URL to NO in the render form fixes the submit blank page. The duplicate port in the link is still present on the chronoconnectivity list though.
Hi sem,
It's not a problem with verification - that will just turn admin messages and strap-lines on and off.
Please check the livesite setting in the site configuration.php file - that should usually be empty. If it has been set and includes the port it would explain this issue.
Bob
It's not a problem with verification - that will just turn admin messages and strap-lines on and off.
Please check the livesite setting in the site configuration.php file - that should usually be empty. If it has been set and includes the port it would explain this issue.
Bob
Hey Bob - live site is blank. I see the root of the problem - the reason it worked on Tuesday is that I was testing it via the LAN.
The server is on an internal dmz - it listens on 443 itself and is fine going to mydomain.local and works perfectly. It also is accessible from the outside from mydomain.com:3443 (firewall using a non standard ssl port). Joomla itself doesn't care about this, but CC and CF do. If I look at the validate installation, they are both showing the url for the installation as mydomain.com:3443:3443
Right now I'm at a loss - I'm guessing cc and cf don't like the non standard ssl port.
mark
The server is on an internal dmz - it listens on 443 itself and is fine going to mydomain.local and works perfectly. It also is accessible from the outside from mydomain.com:3443 (firewall using a non standard ssl port). Joomla itself doesn't care about this, but CC and CF do. If I look at the validate installation, they are both showing the url for the installation as mydomain.com:3443:3443
Right now I'm at a loss - I'm guessing cc and cf don't like the non standard ssl port.
mark
The duplicate port issue has now been fixed by reinstalling CF after CC. I got it the wrong way around.
mark
mark
Hi Mark,
Please check this out with Max using the Contact Us menu above and linking to this thread. I suspect that the GCore library may not be handling the URL correctly in this case.
Bob
Please check this out with Max using the Contact Us menu above and linking to this thread. I suspect that the GCore library may not be handling the URL correctly in this case.
Bob
Hey Bob - I've had an email convo with Max about it - reinstalling latest CF after CC resolved the issue - he'd mentioned that CF 5.0.4 fixed something to do with url handling and it was my mistake to install them in the wrong order. I've now got a tattoo that says "INSTALL CF LAST" in curly writing : )
This topic is locked and no more replies can be posted.
