在Wordpress中调用CodeIgniter get_instance会导致404

时间:2015-07-15 23:32:04

标签: php wordpress .htaccess codeigniter

在过去的一天左右,我一直在努力使用Wordigniter很好地使用Wordpress。我有一个用Codeigniter编写的父应用程序,我正试图用来控制对Wordpress安装的访问。

到目前为止,我已经运气好了,获得了一个Codeigniter实例(通过get_instance())来显示并进行了必要的修改,以使两个应用程序在大多数情况下保持彼此不同。

但是,我现在对着Wordpress网站的root index.php之后的任何事情都不知所措了。

URL看起来像/ parent / content / external / wordpress,其中“parent”是Codeigniter根文件夹,wordpress是Wordpress根文件夹。

我可以加载example.com/parent/content/external/wordpress(带或不带index.php),但像wordpress / sample-page这样的内容会导致Codeigniter 404错误。

似乎Codeigniter正在尝试将URL解析为控制器和方法,但失败了。我在CI日志中收到404错误,指向Wordpress网址的第一部分(上例中的示例页面)。

是否有人知道如何通过推送到Wordpress index.php文件中的代码加载CI以停止尝试解析?

下面粘贴的文件内容。谢谢!

<?php

// BEGIN: CodeIgniter setup

// Remove the query string
$_SERVER['QUERY_STRING'] = '';  

// Include the codeigniter framework
define("REQUEST", "external");
require('/home/magicmag/magicmagazine.com/x/index.php');

// Create CI instance
$CI =& get_instance();

// Authenticate user with custom redirect
$CI->user = $CI->xlib->isLoggedIn(FALSE);

// Custom redirect
if(!$CI->user) {
    redirect('/user/login?d=/content/ext/magic-live-2015');
}

#ToDo: Rewrite this so that the destination is determined by current URL or by the starting URL of the external content

// Check for existing auth
if(!isset($CI->user['ext-magic-live-2015'])) {
    // User isn't currently authenitcated to the external content

    // Try to authentical
    $CI->user['ext-magic-live-2015'] = $CI->xlib->hasExtAccess($CI->user['userId'], '1'); // MAGIC Live is extId 1

    // If authenticated
    if($CI->user['ext-magic-live-2015']) {

        // Store it in the session
        $CI->session->set_userdata('ext-magic-live-2015', $CI->user['ext-magic-live-2015']); #ToDo fix hardcoded name
    } else {
        // Not authenticated
        $CI->session->set_flashdata('danger', 'You do not have access to that content.');
        redirect('/');
    }
}


// END: CodeIgniter setup

// UNEDITED WORDPRESS INDEX.PHP IS BELOW

/**
 * Front to the WordPress application. This file doesn't do anything, but loads
 * wp-blog-header.php which does and tells WordPress to load the theme.
 *
 * @package WordPress
 */

/**
 * Tells WordPress to load the WordPress theme and output it.
 *
 * @var bool
 */

define('WP_USE_THEMES', true);

/** Loads the WordPress Environment and Template */
require( dirname( __FILE__ ) . '/wp-blog-header.php' );

这是Codeigniter .htaccess文件:

<IfModule mod_rewrite.c>
    RewriteEngine On
    RewriteBase /x/

    #Removes access to the system folder by users.
    #Additionally this will allow you to create a System.php controller,
    #previously this would not have been possible.
    #'system' can be replaced if you have renamed your system folder.
    RewriteCond %{REQUEST_URI} ^system.*
    RewriteRule ^(.*)$ /index.php?/$1 [L]

    #When your application folder isn't in the system folder
    #This snippet prevents user access to the application folder
    #Submitted by: Fabdrol
    #Rename 'application' to your applications folder name.
    RewriteCond %{REQUEST_URI} ^application.*
    RewriteRule ^(.*)$ /index.php?/$1 [L]

    #Checks to see if the user is attempting to access a valid file,
    #such as an image or css document, if this isn't true it sends the
    #request to index.php
    RewriteCond %{REQUEST_FILENAME} !-f
    RewriteCond %{REQUEST_FILENAME} !-d
    RewriteRule ^(.*)$ index.php?/$1 [L]
</IfModule>

<IfModule !mod_rewrite.c>
    # If we don't have mod_rewrite installed, all 404's
    # can be sent to index.php, and everything works as normal.
    # Submitted by: ElliotHaughin

    ErrorDocument 404 /index.php
</IfModule>

1 个答案:

答案 0 :(得分:0)

确定你的.htaccess不允许访问word press目录,并会触发任何URI_REQUEST到codeigniter index.php 所以为了允许访问wp目录,添加一个新的条件+规则,如此

#allow access to wp directory 
RewriteCond %{REQUEST_URI} ^parent/content/external/wordpress.*
RewriteRule ^(.*)$ /$1 [L]

所以你的.htaccess看起来像这样

<IfModule mod_rewrite.c>
    RewriteEngine On
    RewriteBase /x/

    #Removes access to the system folder by users.
    #Additionally this will allow you to create a System.php controller,
    #previously this would not have been possible.
    #'system' can be replaced if you have renamed your system folder.
    RewriteCond %{REQUEST_URI} ^system.*
    RewriteRule ^(.*)$ /index.php?/$1 [L]

    #When your application folder isn't in the system folder
    #This snippet prevents user access to the application folder
    #Submitted by: Fabdrol
    #Rename 'application' to your applications folder name.
    RewriteCond %{REQUEST_URI} ^application.*
    RewriteRule ^(.*)$ /index.php?/$1 [L]

    #Checks to see if the user is attempting to access a valid file,
    #such as an image or css document, if this isn't true it sends the
    #request to index.php
    RewriteCond %{REQUEST_FILENAME} !-f
    RewriteCond %{REQUEST_FILENAME} !-d
    RewriteRule ^(.*)$ index.php?/$1 [L]

    #allow access to wp directory 
    RewriteCond %{REQUEST_URI} ^parent/content/external/wordpress.*
    RewriteRule ^(.*)$ /$1 [L]

</IfModule>

<IfModule !mod_rewrite.c>
    # If we don't have mod_rewrite installed, all 404's
    # can be sent to index.php, and everything works as normal.
    # Submitted by: ElliotHaughin

    ErrorDocument 404 /index.php
</IfModule>

你可以在这里测试.htaccess http://htaccess.madewithlove.be/

当你提出要求时 例如,parent/content/external/wordpress/11/22/33

您将被重定向到wp而不被抓住&#39; by ci index.php

如果它仍然无法正常播放

RewriteCond %{REQUEST_URI} ^parent/content/external/wordpress.*

一点点

希望有所帮助