Databases
StackOverflow2013
Postsdbo
POExclude a URL from rewrite in .htaccess with "last" flag
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POExclude a URL from rewrite in .htaccess with "last" flag
    primarykey
    data
    text
    <p>WordPress has been installed as a blog into osCommerce. I'm trying to get the WordPress RSS feed to work. All WP core files exist, but I get all kinds of errors accessing the feed at mydomain.com/wordpress/feed/, like 404s, "the feed can't be updated because the source file is no longer available," or even raw php code in the browser from the osCommerce feed file.</p> <p>I think the problem is the rewrite rules for osCommerce, and I'm thinking if I can exclude the WP feed URL from rewrite, it will fix the feed or help find the real issue.</p> <p>Looking around SO, I found a solution to use the "last" flag on a URL to prevent it from being rewritten. Problem is, the existing .htaccess already has a rule with a "last" flag on it.</p> <p>Is there a way to not rewrite the WP feed URL? Can another "last" rule be added? I'd like to have some definite things to try before messing with .htaccess to avoid disrupting the site.</p> <pre><code>RewriteEngine On RewriteBase / RewriteCond %{REQUEST_FILENAME} !-f RewriteCond %{REQUEST_FILENAME} !-d RewriteRule ^(.*)/$ http://www.mydomain.com/index.php?cPath=$1 [L] RewriteRule ^(.*)-p-([0-9]+).html$ product_info.php?products_id=$2&amp;%{QUERY_STRING} RewriteRule ^(.*)-c-([0-9]+).html$ index.php?cPath=$2&amp;%{QUERY_STRING} RewriteRule ^(.*)-m-([0-9]+).html$ index.php?manufacturers_id=$2&amp;%{QUERY_STRING} RewriteRule ^(.*)-pi-([0-9]+).html$ popup_image.php?pID=$2&amp;%{QUERY_STRING} RewriteRule ^(.*)-pr-([0-9]+).html$ product_reviews.php?products_id=$2&amp;%{QUERY_STRING} RewriteRule ^(.*)-pri-([0-9]+).html$ product_reviews_info.php?products_id=$2&amp;%{QUERY_STRING} RewriteRule ^(.*)-t-([0-9_]+).html$ articles.php?tPath=$2&amp;%{QUERY_STRING} RewriteRule ^(.*)-au-([0-9]+).html$ articles.php?authors_id=$2&amp;%{QUERY_STRING} RewriteRule ^(.*)-a-([0-9]+).html$ article_info.php?articles_id=$2&amp;%{QUERY_STRING} # Information pages RewriteRule ^(.*)-i-([0-9]+).html$ information.php?info_id=$2&amp;%{QUERY_STRING} RewriteRule ^(.*)-links-([0-9_]+).html$ links.php?lPath=$2&amp;%{QUERY_STRING} RewriteRule ^(.*)-n-([0-9]+).html$ newsdesk_info.php?newsdesk_id=$2&amp;%{QUERY_STRING} RewriteRule ^(.*)-nc-([0-9]+).html$ newsdesk_index.php?newsPath=$2&amp;%{QUERY_STRING} RewriteRule ^(.*)-nri-([0-9]+).html$ newsdesk_reviews_info.php?newsdesk_id=$2&amp;%{QUERY_STRING} RewriteRule ^(.*)-nra-([0-9]+).html$ newsdesk_reviews_article.php?newsdesk_id=$2&amp;%{QUERY_STRING} </code></pre>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USmarkratledge
    1. USmarkratledge
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POExclude a URL from rewrite in .htaccess with "last" flag
      1. This table or related slice is empty.
      1. VTUpMod
    1. COIs this your complete .htaccess? If there’s more, show us.
      singulars
      1. POExclude a URL from rewrite in .htaccess with "last" flag
      1. USfuxia
    2. COIt's all there now; I had thought the last flag line was the most important....
      singulars
      1. POExclude a URL from rewrite in .htaccess with "last" flag
      1. USmarkratledge
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload