I have deployed my code at GoDaddy, and I am experiencing problems. I have spent a couple of hours now trying to debug why both pagination and sorting has stopped working. This is working in my development environment of course.
Pretty much stuck here so far, wondering if this might be an Mysql versioning problem or something.
If anyone has a clue or suggestion, I would be happy to hear it
After some debugging what I now see is that I cannot get/use GET parameters from my Yii code. But deploying a php file and echoing the get parameter, it works. This is pretty weird.
can you post the view you are using to display the data. Are you using a widget i.e. grid or list? if so, check in your browser if you have the script section created at the bottom and the generated assets folder in the header section - might be blocked permissions to create new folders for the on-the-fly assets folders.
My pagination and sorting does not work, as the CListView is giving me e.g.
?sort=title
but if I manually change this in the address field to
/sort/title
it is working.
Of course, this could be solved by changing the yii widget (CListView), but that seams like a very bad solution.
Also, changing to an AJAX functionality on the sorting can help (I guess, without checking into the details), but that only fixes the sorting / pagination issues and not the other (very much needed) GET parameters I have.
if you have your url manager configured (in main.php) then you should be able to use both, and the server (i.e. apache) will make the alias change. However, this goes together with your .htaccess set in you app’s root.
Option 1: you forgot to ftp the .htaccess file to the server
Option 2: your godaddy server configuration has url management already configured and its conflicting with your setting (that would explain the example you mentioned above)
Option 3: godaddy are limiting your .htaccess override permissions, its known that they do that for Windows hosting, but you are on linux so that shouldn’t happen.
I would comment out the urlManager component from the config and see if that fixes the issues and work from there.
I will verify the url management by the hosting provider, but I really believe that this is not an issue.
I am able to override the rewrite settings, otherwise I would not be able to have /controller/action, would I?
I tried to comment out the RewriteEngine = On in my .htaccess and then the /controller/action path did not work, so I presume this is working correctly.
Dagfinn, all these functions - pagination/sort by default call the controller’s createUrl method with the page information. You can override this method in your controller to support the URL scheme you want.