Forum Replies Created

Viewing 15 replies - 1 through 15 (of 47 total)
  • Thread Starter rexgoode

    (@rexgoode)

    Thanks for the reply. I deactivated powerpress. Only planned to use it. Haven’t yet. I still get the errors not related to powerpress. The problem seems to be that it doesn’t recommend any subdomains that are linked from WP.

    Thread Starter rexgoode

    (@rexgoode)

    Thanks for the reply, @bcworkz. Yes, I do go through admin-ajax.php.

    Here’s an attempt at showing the code, leaving out things I’m pretty sure are irrelevant for brevity’s sake. From the php that handles the class:

            if (!class_exists("ivevents")) {
                    class ivevents {
                            var $dbVersion = "0.0";
    ... various class attributes
                            public function ivevents() { // constructor
    ... constructor-like stuff
                            }
                            function ivevents_request() {
    //                              $hasAuthority = current_user_can("edit_posts");
    //                              if (wp_verify_nonce($nonce, "ivev_general_nonce")) {
                                            if (isset($_REQUEST['ivevaction'])) {
                                                    switch($_REQUEST['ivevaction']) {
                                                            case 'action':
                                                                    $success = TRUE;
                                                                    $result = array("sample" => "return data");
                                                                    $ret = array("success" => $success, "data" => $result);
                                                                    header("Content-type: application/json");
                                                                    echo json_encode( $ret );
                                                                    exit;
                                                                    break;
                                                            case 'Cancel':
                                                            default:
                                                                    break;
                                                    }
                                            }
    //                              }
                            }
    ...

    In the main php file:

    include_once( ABSPATH . 'wp-admin/includes/plugin.php' );
    function ivevents_enqueuer() {
    ... set up CSS
            $regscript = wp_register_script( "iveventsscript", plugins_url("ivevents/ivevents.js"), array('jquery') );
            wp_localize_script('iveventsscript', 'IVEventsAjax', array( 'ajaxurl' =>  admin_url( 'admin-ajax.php'), 'ivev_nonce' => wp_create_nonce('ivev_general_nonce' )));
            wp_enqueue_script( 'iveventsscript');
    }
    add_action( 'wp_enqueue_scripts', 'ivevents_enqueuer' );
    add_action( 'admin_enqueue_scripts', 'ivevents_enqueuer' );
    
    $adminurl = get_option('siteurl').'/wp-admin';
    $sep = (strpos(__FILE__,'/')===false)?'\\':'/';
    $WPpluggable = substr( dirname(__FILE__),0,strpos(dirname(__FILE__),'wp-content')) . 'wp-includes'.$sep.'pluggable.php';
    if ( file_exists($WPpluggable) )
            require_once($WPpluggable);
    include("classes/events.php");
    if (class_exists("ivevents")) {
            $ivev = new ivevents();
    } // Create an object of type ivevents
    if (isset($ivev)) {
            add_action( 'wp_ajax_ivevaction', array($ivev, 'ivevents_request'));
    }
    

    Rex

    Thread Starter rexgoode

    (@rexgoode)

    Unfortunately, while this solves the problem I was having with WordPress Subdomains, it creates a problem for other subdomains. For example,
    if I do webmail.domain.com, instead of taking me to the right page for that, I end up in WordPress at the wp-signup.php address. There must be a way to have it both ways.

    Thread Starter rexgoode

    (@rexgoode)

    It did. I might be having a problem with other subdomains on the site that aren’t part of WP. I’m looking into it.

    Thread Starter rexgoode

    (@rexgoode)

    I have solved my problem by the following:

    Things I checked

    I had a DNS entry: *.domain.com, A, IP Address.

    Things I changed

    I added the following line to vhost.conf in the same directory as httpd.conf.

    ServerAlias "*.domain.com"

    Things I ran

    The reconfigure command for my server, in my case, httpdmng --reconfigure-all
    Followed by apachectl graceful

    I did this on the two domains I know were having this problem. Now I’m going to check them all.

    Thread Starter rexgoode

    (@rexgoode)

    No permissions were changed by the host. The error_log has the same errors as the console.

    I’ve deleted the database and reinstalled WordPress v4.5.3. It works. I can log in. I’ve lost the posts, pages, and themes. I have a backup of the database, but I think that restoring it from backup will create the problem again. I’ll try it for now. It must’ve been a file permission problem that the reinstall corrected. I think I’ll mark this as resolved and post about any future problems on a new thread.

    Thanks for the feedback.

    Thread Starter rexgoode

    (@rexgoode)

    Thanks, kjodle. It looks like a good plugin.

    Thread Starter rexgoode

    (@rexgoode)

    Thank you! Again!

    That works!

    Thread Starter rexgoode

    (@rexgoode)

    I always went with subdomain. I did try a security plugin that modified the .htaccess and then uninstalled it because it was throwing too many errors in my phperrors log. I went to a back of .htaccess to get it back. Maybe I went to the wrong backup. What should it say?

    Thread Starter rexgoode

    (@rexgoode)

    RewriteEngine On
    RewriteBase /
    RewriteRule ^index\.php$ - [L]
    
    # add a trailing slash to /wp-admin
    #########RewriteRule ^wp-admin$ wp-admin/ [R=301,L]
    RewriteRule ^([_0-9a-zA-Z-]+/)?wp-admin$ $1wp-admin/ [R=301,L]
    
    RewriteCond %{REQUEST_FILENAME} -f [OR]
    RewriteCond %{REQUEST_FILENAME} -d
    RewriteRule ^ - [L]
    RewriteRule ^([_0-9a-zA-Z-]+/)?(wp-(content|admin|includes).*) $2 [L]
    RewriteRule ^([_0-9a-zA-Z-]+/)?(.*\.php)$ $2 [L]
    #########RewriteRule ^(wp-(content|admin|includes).*) $1 [L]
    #########RewriteRule ^(.*\.php)$ $1 [L]
    RewriteRule . index.php [L]

    This is an old thread, but I still want to chime in. I’ve tried some very complex combinations of characters for a password, even just closed my eyes and hit keys at random. I’ve used combinations of upper, lower, characters, numbers and still it gets tagged as very weak. Sometimes I can get a “strong” by a very long sequence of such garbage or sometimes even a short one. There are a lot of things that fail the test that shouldn’t. It took me an hour to come up with something I could remember and that passed as “strong”.

    I know that a strong password isn’t required by WordPress, but a few good plugins do. I ought to be able to create a memorable, strong password in a whole lot less than an hour.

    Thread Starter rexgoode

    (@rexgoode)

    Yes, it is a sub site. I’ve had to do the create table select thing on all of my installations (domains) for those that have subdomains and all of those subdomains existed a couple of years before I found your plugin. None of the tables got created at the time I installed your plugin. I’ve created them all manually and they work.

    Thread Starter rexgoode

    (@rexgoode)

    A quick follow-up. I figured out that since I have a network aka multisite installation, that there are more directories under the backups directory that need attention as far as file permissions are concerned. Fixed the file permissions and ownership issues and it works now.

    Thought I’d add that here in case anyone else might need the info.

    Thanks again for the great plugin.

    Thread Starter rexgoode

    (@rexgoode)

    Thanks for the explanation. Looking forward to additional features.

    I do have the cookie-based brute force prevention enabled. It is working well, but I still get a lot of attacks. Thanks to your plugin, they aren’t bringing servers to their knees.

    Go back and check the instructions again. Your wp-config.php and most likely, your .htaccess files are not quite right. There should have been a point in the process where you were asked to copy certain code into both files. It looks like you missed something. If you start with your wp-config-sample.php file again and fill in the right database login information, you can do the whole process over. Do the steps exactly, especially making sure to carefully put the right code into .htaccess and wp-config.php. Also, check the permissions on all of your root directory files.

Viewing 15 replies - 1 through 15 (of 47 total)