handlegeek

You can enable permission for authenticated users to add content of the type "reverse-auction" or whatever you have named it. Then users of the site can add content using http://example.com/node/add/reverse-auction

Unless I am misunderstanding what you are expecting, you can target your sub domain like this correct? RewriteEngine On RewriteCond %{HTTP_HOST} ^sub\.example\.com$ [NC] RewriteRule ^(/)?$ index.php?page=pressrelease_homepage [L] RewriteRule ^index([0-9-]+)\.html$ index.php?page=pressrelease_homepage&pn=$1 [L] RewriteRule ^([a-zA-Z0-9-]+)-([0-9-]+)\.html$ index.php?page=pressrelease_page&id=$2 [L]

Guess this will work for you RewriteEngine On RewriteCond %{HTTP_HOST} ^example\.com [NC] RewriteRule ^news http://press.example.com/ [R=301,L] RewriteRule ^press/(.*)$ http://press.example.com/$1 [R=301,L]

If you can give couple of examples of redirect you want to do - it would be better. Both /press and /news to press.site.com is kind of confusing. A simple rewrite for example.com/press/something to press.example.com/something would be like the one below RewriteEngine On RewriteCond %{HTTP_HOST} ^example\.com [NC] RewriteRule ^press/(.*)$ http://sub.example.com/$1 [R=301,L] Believe you are expecting something different mentioning about old urls and new urls for SEO. Examples would illustrate better.

Try to have a URL pattern like /service to be more specific and not apply to images/static files. For example http://123.domain.com/service/456 -> http://www.domain.com/index.php?page=Profile&user=123&services_id=456 Following rule will work: RewriteEngine On RewriteCond %{HTTP_HOST} !^www.domain\.com$ [NC] RewriteCond %{HTTP_HOST} ^(.+)\.domain.com$ [NC] RewriteRule ^service/(.*)[$ index.php?page=Profile&user=%1&services_id=$1 [L]

Yes, you can use PHP to check if the URL starts with "http://" or "https://" and show error message OR prefix "http://" considering http:// to be default. In addition to that, using JavaScript you can validate the URL field - To check if it follows a valid URL pattern and show a error message to the user.

You can check if the AJAX request is successful by looking into the request and response in your browser: Firefox -> Firebug or Chrome Web Inspector "Net" tab. This will show the request parameters and the response (including headers) of the Ajax request which will help in debugging the issue.