Jarod Thornton

I managed to figure this out!

From the admin options page I have this text form:

echo '<table class="form-table">' . "\n";

			echo '<tr valign="top">'
			. '<th scope="row">'
			. __('DudaMobile Username', 'mobile-xml-sitemaps')
			. '</th>'
			. '<td>'
			. '<p>'
			. __('Enter your DudaMobile username', 'mobile-xml-sitemaps')
			. '</p>' ."\n"
			. '<input type="text" name="duda_mobile_username"'
                . ' class="widefat code"'
                . ' value="' . esc_attr($options['duda_mobile_username']) . '"'
                . ' />'
			. '</td>'
			. '</tr>';

		echo "</table>\n";

To pass that value along to the utils page to construct my URL:

$this->write(
						'https://m.'.$_SERVER[HTTP_HOST].'/site/'.$this->duda_mobile_username.'/default?='.get_pagenum_link($i),

$this->duda_mobile_username was all it took ??

I modified the code a little and cleaned it up.

// Set exlusion for home page referrer, page pages, category pages, archive pages
$exlusion =
(get_the_ID() == 0) == (url_to_postid(wp_get_referer()))
|| is_page() || is_category() || is_archive() || is_front_page();
// Grab the title of referring page
if (!$exlusion) {
	if (!empty($_SERVER['HTTP_REFERER'])) {
		if (parse_url($_SERVER['HTTP_REFERER'], PHP_URL_HOST) == $_SERVER['HTTP_HOST']) {
			$referring_page_title =
			get_the_title( url_to_postid(wp_get_referer()) );
			// Set the conditions and create back link
			echo '<a href="Javascript:window.history.back();">? Back to '.$referring_page_title.'</a>';
		}
	}
}
// Yay it works!

I hope someone finds this useful.

Ok I figured it out!

Here’s the modified code that checks to see if the referring site is external source, home page, page, category, archive and if it is one of the two does nothing but if it is not it shows a window.history.back link with the referring page title

$refering_page_title = get_the_title( url_to_postid(wp_get_referer()) );
if (is_page() || is_category() || is_archive() || url_to_postid(wp_get_referer()) == 0)
{
	}
elseif (!empty($_SERVER['HTTP_REFERER']))
{
    if(parse_url($_SERVER['HTTP_REFERER'], PHP_URL_HOST) == $_SERVER['HTTP_HOST'])
    {
        echo '<a href="window.history.back();">? Back to '.$refering_page_title.'</a>';
    }
}

I struggled with this but I found a work-around that seems to do the trick.

<?php if ( has_post_thumbnail() ) : ?>

                        <?php $large_image_url = wp_get_attachment_image_src( get_post_thumbnail_id( $post->ID ), 'large' );?>
						<a class="artist-page" href="<?php the_permalink(); ?>">
                        <div class="artist-page-div" style="background:url(<?php echo $large_image_url[0]; ?>) no-repeat  center;">
						</div></a>
					<?php endif; ?>

This effectively gives me control of the thumbnail and offers the flexibility to work within the artist-page-div div itself.

I would still like to know how I can set custom thumbnail sizes as requested above.

Hi Gerroald,

I did in fact go through and troubleshoot the problem by disabling plugins etc. I had to manually disable the plugins prior to disabling WP Security because disabling more than one from admin caused crazy memory problems on our VPS and timed out. Of all the plugins I disabled and tweaked settings, our multisite only acted like it should after your plugin was disabled. I really like the plugin too ??

There are several issues involving this plugin but also other plugins. It took a combination of disabled plugins to finally get things working. Our VPS was forced to reboot many times over the last several months and some of the security features didn’t act right or consistent.

Anyway, for the time being I’ve had to disable several plugins including this and default to utilizing certain .htaccess related security work-around solutions as well as other stuff. I don’t have time to figure out where in our network these other problems are originating from interim so I will check back on iThemes WP Security and likely pay for your support to assist in the ideal configuration.

Thank you for your response btw.

I’m glad someone else is experiencing this mysterious settings reset, as tmcgraw outlines.

Literally, I go into the iThemes security settings and set all the check boxes (since it somehow reset a few updates ago). The most important to me is the hide-backend feature.

Literally, I set all these settings, five minutes later I try to login to another site on the network and my hidden URL is broken…

I have a nice 404 page that recognizes the compatibility slug and checks the referring address – if the hidden URL feature is turned off, the 404 redirects after ten seconds to the normal /wp-admin so my clients won’t get upset about not being able to access – but of course if it’s not hidden I get a lot of would be hackers trying to get in.

I’m curious why this is happening. I’m 99.9% sure my login and password is uncompromised and I’m the only super admin etc – no one is actually getting into the site.

Any feedback on this?

I was wrong about the error only being present on the root site. It is affecting all sites with this plugin activated.

One strange behavior we observed is the widgets and drop down menus were not working until we performed a reset on the plugin. However upon re-authenticating the account we now experience an API service error 400 and 403 Error calling GET. This error appears on the settings page and breaks the account selection drop down.

Any insight is greatly appreciated!

I see. Learn something new haha.

That did the trick! It also revealed that I have to declare the size in CSS for things like top

top:10;

doesn’t work anymore with that doc dec.

top:10px;

does…

Did you see this on your site? On ours the header starts with <html <?php language_attributes(); ?>> and doesn’t affect the site at all.

Your markup would obviously need addressed as you have the php tag between the m and l of html.

I still can’t get it working

I am experiencing the exact issues as referenced above. Anything using the jQuery Colorbox for handling lightboxes does the same thing, opens too low in the page / overlaps bottom edge of screen.

I’ve tried removing ALL stylesheets, other plugins without any luck. This is on a MultiSite and plenty of other sites using this in the same manner have no issues. I cannot figure this out :/

Example site: https://paintsolutionsky.com/photos/

Any insight is greatly appreciated.

Update: Ok so apparently it is only an error on the root domain of the MultiSite network.

We use virtual directories and both mapped domains and sites yet to be mapped but with this plugin already configured and authenticated appear to be working fine.

Nonetheless, insight on resolving this for our root site is much appreciated.

Following up on my post @ post link I want to share the final resolve.

We have a network with a few hundred sites and it was a headache dealing with this issue at first. Then I was able to proceed with admin after applying the resolve mentioned in my original post. However an hour or so later I returned to find support inquiry regarding clients unable to login (we have a no-index login link on all our sites hidden bottom right corner of screen for clients). Sure enough it wasn’t working, again.

Anyway, I went ahead and looked through my .htaccess and the iThemes settings, made sure the hide backend login was disabled and noticed we had some new updates. One such update was for iThemes.

After I updated to the latest release (at the time 4.0.16), then re-enabled the backend option, it worked as expected.

I just updated to 4.0.19 and all is good.

I’m posting this to be helpful to anyone who might experience similar issues as discussed here. It may not be a hassle at all to resolve a problem you may be having. I’ve read several comments about dropping iThemes security plugin due to related problems. iThemes has a great product free of charge and works exceptionally well IMO. It’s worth taking a moment and troubleshooting the basics like what I’ve outlined and moving onto the more advanced stuff mentioned here as well.

My $0.2

I posted this over here but thought it would be helpful on this thread as well.

I ran into the same problem this morning, specifically with the hide backend option.

After reading through and seeing there was a “reset” required, I disabled that option. The setting remained in my .htaccess of course, but with the option disabled (.htaccess unchanged) I was able to login at my hidden URL. Upon enabling that setting once more it works as expected.

Hope this is helpful. Simple fix for me.

I ran into the same problem this morning, specifically with the hide backend option.

After reading through and seeing there was a “reset” required, I disabled that option. The setting remained in my .htaccess of course, but with the option disabled (.htaccess unchanged) I was able to login at my hidden URL. Upon enabling that setting once more it works as expected.

Hope this is helpful. Simple fix for me.

I thought I would follow up and see if there are any developments on an update for this functionality, make SFB available to other user roles, namely editors.

I’m working on a support admin area for my clients (going very well) and stumbled on some information that *might* be insightful.

If you’re running into the ?You do not have sufficient permissions to access this page.? message in a wp_die() screen, then you’ve hooked too early. The hook you should use is admin_menu.

This isn’t related to what I am currently working on, but is relevant to SFB as it’s the message that is displayed at editor role.

I’ve reviewed the source of your (awesome) plugin and was not able to see anything that would cause this (but I know very little) and thought it was worth sharing.

Looking forward to an update.

Thanks again, Pippin.