No friends yet.
I did a search and didn't find rewrite.php anywhere in the elgg 1.8.3 I downloaded yesterday. I couldn't find anything with rewrite in the file name actually. I did write a basic rewrite rule and that worked. I also verified that mod_rewrite is loaded. I'll take a look at the workaround Andras suggested and see what happens. This is just a test install on a test server so no harm done by poking around.
Cash, let me know what info I can get for you to help.
rewrite.php does not exist. In .htaccess there is a rewrite rule that routes requests for that file back to the installer.
So are you saying that if you hit the rewrite.php page in your browser, it works?
I see it now... and no, it doesn't work. I do have other rewrite rules on other parts of the site working fine. I worked around the problem as Andras suggested and got it installed.
In the .htaccess I commented out <IfModule mod_rewrite.c> and it's corresponding </IfModule> to force the rewrite to turn on and the rules to kick in. Pointing the browser to rewrite.php yields success.
Finally back from vacation so I can get back to this...
Thanks for the response. I'm still figuring out the architecture of ELGG and where to find everything. Can you point me in the direction of where I would put such a statement?
I seem to have found my answer...
The file mod/profile/views/default/profile/listing.php actually compiles the information to put in the member search listing around line 39. That is then passed to views/default/entities/entity_listing.php to be output.
That sounds right for Elgg 1.7. I think we cleaned this up in Elgg 1.8 so that it uses the view user/default. This makes it more consistent with the other entities in Elgg. A blog maps to the view object/blog, a group maps to group/default, and so on. It is <type>/<subtype>.
You might want to check out this plugin to help with finding the right views: http://community.elgg.org/pg/plugins/project/714742/developer/aszepeshazi/content-debugger