CrimsonMoon

Okay, I figured it out. I went into content-features.php and edited it to say:

<article id="id-<?php the_ID(); ?>" <?php post_class( 'span_1_of_5' ); ?>>

Same! Updated to version 4.0.2 and everything went smoothly. ?? Thanks for the quick response to this issue!

I had to delete everything related to iTheme in the .htaccess file, including:

# BEGIN iThemes Security
# END iThemes Security

Tried updating to version 4.0.1 and still got the 500 internal server error. I’m reverting to the last version until I hear that this issue has been fixed.

Yup, still had to clean the .htaccess file of iThemes code…

Same thing happened to me. I’m deleting the plugin folder and uploading an older version…

I too have disabled/enabled and uninstalled/installed, but there was no change. I just checked the Roles settings, and everything is set to Administrator, which is what I’m signed in as. My theme is a custom adaptation of the default WordPress 2012 theme. Must be one of my other plugins that’s causing the issue.

Same problem here…

Figured it out! I had to change the action to the page so that the results displayed on the same page and not on the default WordPress search.php. Then I used PHP to do an if statement on the set of users that I already generated.

<form  method="post" action="<?php the_permalink(); ?>"  id="searchform">
            <input type="text" id="search" name="search" value="" />
            <input type="submit" value="Search" id="searchsubmit" />
	    </form>

<?php if( isset( $_REQUEST['search'] ) ) {
  $name = $_POST['search'];
  foreach ($allusers as $auser) {
  if (stristr($auser['first'], $name) || stristr($auser['last'], $name)) { ?>

Unfortunately, I don’t have any logs at the moment. I encountered this error on a live website, and will not be able to mess with it for about a month. It most likely clashed with another plugin that I’m running.

Did anyone make the proper code for this already? I’m not great at modifying plugins…

Ok, thanks! After you said this, I realized that though it wasn’t present in the .htaccess file at the root of the install, it was in the .htaccess file for the main directory containing the install directory.

Thank you so much for bringing me clarity!