Databases
StackOverflow2013
Postsdbo
POKohana and OpenX
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POKohana and OpenX
    primarykey
    data
    text
    <p>I am trying to install OpenX in a website that I use Kohana. It worked fine, until I found this error:</p> <blockquote> <p>Fatal error: Uncaught Kohana_Request_Exception [ 0 ]: Unable to find a route to match the URI: 500.shtml ~ SYSPATH/classes/kohana/request.php [ 635 ] thrown in /home/xxxxxx/public_html/plugb/system/classes/kohana/request.php on line 635</p> </blockquote> <p>The url is: <a href="http://www.plugb.com/openx/www/admin/plugins/oxMarket/market-campaign-edit.php?clientid=1&amp;campaignid=" rel="nofollow noreferrer">http://www.plugb.com/openx/www/admin/plugins/oxMarket/market-campaign-edit.php?clientid=1&amp;campaignid=</a></p> <p>My current .htaccess is:</p> <pre><code># Turn on URL rewriting RewriteEngine On # Installation directory RewriteBase / # WWW RewriteCond %{HTTP_HOST} !^www\.plugb\.com [NC] RewriteRule ^(.*)$ http://www.plugb.com/$1 [R=301,L] #remove trailing slashes RewriteCond %{HTTP_HOST} !^\.plugb\.com$ [NC] RewriteCond %{REQUEST_FILENAME} !-f RewriteCond %{REQUEST_FILENAME} !-d RewriteRule ^(.+)/$ http://%{HTTP_HOST}/$1 [R=301,L] # Protect hidden files from being viewed &lt;Files .*&gt; Order Deny,Allow Deny From All &lt;/Files&gt; # Protect application and system files from being viewed RewriteRule ^(?:application|modules|system)\b.* index.php/$0 [L] # Allow any files or directories that exist to be displayed directly RewriteCond %{REQUEST_FILENAME} !-f RewriteCond %{REQUEST_FILENAME} !-d # Rewrite all other URLs to index.php/URL RewriteRule .* index.php/$0 [PT,L] Redirect 301 /gamesindex / </code></pre> <p>Why am I getting this error? How can I fix it?</p> <p>Thank you, Gabriel.</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. This table or related slice is empty.
    1. USGabriel Bianconi
    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. This table or related slice is empty.
    1. COThat error suggests that you were getting another internal server error (and the server tried to generate the 500 error response, but the request was grabbed by the Kohana route handler since the `ErrorDocument` doesn't really exist). So, to fix this fully you need to resolve the internal server error too. What does your server's error log say?
      singulars
      1. POKohana and OpenX
      1. USTim Stone
    2. CO[23-Aug-2010 20:21:40] PHP Fatal error: Uncaught Kohana_Request_Exception [ 0 ]: Unable to find a route to match the URI: 500.shtml ~ SYSPATH/classes/kohana/request.php [ 635 ] thrown in /home/bianconi/public_html/plugb/system/classes/kohana/request.php on line 635 [23-Aug-2010 21:05:21] PHP Fatal error: Uncaught Kohana_Request_Exception [ 0 ]: Unable to find a route to match the URI: 403.shtml ~ SYSPATH/classes/kohana/request.php [ 635 ] thrown in /home/bianconi/public_html/plugb/system/classes/kohana/request.php on line 635 And other lines similar to this.
      singulars
      1. POKohana and OpenX
      1. USGabriel Bianconi
    3. COWhat about Apache's error log though? That appears to be PHP's.
      singulars
      1. POKohana and OpenX
      1. USTim Stone
 

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