Nathaniel Bailey

Me and the tech guys have been looking into it, and it seems its because I have my WP installed in a different directory then the root.

So it looks like I will have to move my WP install to the root folder rather then /folder

Ok thanks Allen, I will give that a look tomorrow as I can’t be bothered to do anymore tonight lol

And the re-install didn’t help, so its likely to be something to do with the server setup or a security set up, as I remember reading in the past that some security bits can give 404’s in wordpress, so I will have search tomorrow as suggested and ask the tech guys to do the same ??

My sites hosted on a major host not a local machine etc.

I will try to uninstall and re-install the plugin to see if that helps!

Ok thanks for trying to help Daniel, I will just have to see how it works out and maybe look into editing user permissions at a later date if I need to ??

Curious, why would you want to let them publish their post, but not edit?

Because subscribers can submit guest posts, so for security and spam reasons etc I don’t want them to be able to edit their posts once they are live, I should have said subscribers not authors because that’s a different user group.

Sorry was being a little blond by the looks of it, the emails where sent to the spam folder for some reason so all is good on that side of things ??

My question still stands about the editing posts permissions though, I need post authors to only have permission to edit posts which are not published/live on the site?

Thanks for the update Arne, my wp aint showing it in the updates area yet, any idea when this should be available to update via wp admin?

It was the update that I just done that had the warnings in the admin area (the same with all the other threads), so I thought I would share the code I did to fix it and remove the warnings ??

I just update my all in one fav icon plugin too and had the same warnings, but its a simple fix and just a little mistake in the coding of that file.

Simply head to the file in the warning and change the following lines of code from:

'frontendICO' => _('ICO',AIOFAVICON_TEXTDOMAIN),
        'frontendGIF' => _('GIF',AIOFAVICON_TEXTDOMAIN),
        'frontendPNG' => _('PNG',AIOFAVICON_TEXTDOMAIN),
        'frontendApple' => _('Apple Touch Icon',AIOFAVICON_TEXTDOMAIN)
      );

      //mapping of favicon types to translatable Strings
      $this->aioFaviconBackendMap = array(
        'backendICO' => _('ICO',AIOFAVICON_TEXTDOMAIN),
        'backendGIF' => _('GIF',AIOFAVICON_TEXTDOMAIN),
        'backendPNG' => _('PNG',AIOFAVICON_TEXTDOMAIN),
        'backendApple' => _('Apple Touch Icon',AIOFAVICON_TEXTDOMAIN)

Change to:

'frontendICO' => __('ICO',AIOFAVICON_TEXTDOMAIN),
        'frontendGIF' => __('GIF',AIOFAVICON_TEXTDOMAIN),
        'frontendPNG' => __('PNG',AIOFAVICON_TEXTDOMAIN),
        'frontendApple' => __('Apple Touch Icon',AIOFAVICON_TEXTDOMAIN)
      );

      //mapping of favicon types to translatable Strings
      $this->aioFaviconBackendMap = array(
        'backendICO' => __('ICO',AIOFAVICON_TEXTDOMAIN),
        'backendGIF' => __('GIF',AIOFAVICON_TEXTDOMAIN),
        'backendPNG' => __('PNG',AIOFAVICON_TEXTDOMAIN),
        'backendApple' => __('Apple Touch Icon',AIOFAVICON_TEXTDOMAIN)

All that I have done is added an extra _ to each line (changing each _ to _e would also work, but I thought adding another _ looked easier to the eye when checking over the code in the future), which fixes the problem and will stop displaying the warnings ??

I just update my all in one fav icon plugin too and had the same warnings, but its a simple fix and just a little mistake in the coding of that file.

Simply head to the file in the warning and change the following lines of code from:

'frontendICO' => _('ICO',AIOFAVICON_TEXTDOMAIN),
        'frontendGIF' => _('GIF',AIOFAVICON_TEXTDOMAIN),
        'frontendPNG' => _('PNG',AIOFAVICON_TEXTDOMAIN),
        'frontendApple' => _('Apple Touch Icon',AIOFAVICON_TEXTDOMAIN)
      );

      //mapping of favicon types to translatable Strings
      $this->aioFaviconBackendMap = array(
        'backendICO' => _('ICO',AIOFAVICON_TEXTDOMAIN),
        'backendGIF' => _('GIF',AIOFAVICON_TEXTDOMAIN),
        'backendPNG' => _('PNG',AIOFAVICON_TEXTDOMAIN),
        'backendApple' => _('Apple Touch Icon',AIOFAVICON_TEXTDOMAIN)

Change to:

'frontendICO' => __('ICO',AIOFAVICON_TEXTDOMAIN),
        'frontendGIF' => __('GIF',AIOFAVICON_TEXTDOMAIN),
        'frontendPNG' => __('PNG',AIOFAVICON_TEXTDOMAIN),
        'frontendApple' => __('Apple Touch Icon',AIOFAVICON_TEXTDOMAIN)
      );

      //mapping of favicon types to translatable Strings
      $this->aioFaviconBackendMap = array(
        'backendICO' => __('ICO',AIOFAVICON_TEXTDOMAIN),
        'backendGIF' => __('GIF',AIOFAVICON_TEXTDOMAIN),
        'backendPNG' => __('PNG',AIOFAVICON_TEXTDOMAIN),
        'backendApple' => __('Apple Touch Icon',AIOFAVICON_TEXTDOMAIN)

All that I have done is added an extra _ to each line (changing each _ to _e would also work, but I thought adding another _ looked easier to the eye when checking over the code in the future), which fixes the problem and will stop displaying the warnings ??

I just update my all in one fav icon plugin too and had the same warnings, but its a simple fix and just a little mistake in the coding of that file.

Simply head to the file in the warning and change the following lines of code from:

'frontendICO' => _('ICO',AIOFAVICON_TEXTDOMAIN),
        'frontendGIF' => _('GIF',AIOFAVICON_TEXTDOMAIN),
        'frontendPNG' => _('PNG',AIOFAVICON_TEXTDOMAIN),
        'frontendApple' => _('Apple Touch Icon',AIOFAVICON_TEXTDOMAIN)
      );

      //mapping of favicon types to translatable Strings
      $this->aioFaviconBackendMap = array(
        'backendICO' => _('ICO',AIOFAVICON_TEXTDOMAIN),
        'backendGIF' => _('GIF',AIOFAVICON_TEXTDOMAIN),
        'backendPNG' => _('PNG',AIOFAVICON_TEXTDOMAIN),
        'backendApple' => _('Apple Touch Icon',AIOFAVICON_TEXTDOMAIN)

Change to:

'frontendICO' => __('ICO',AIOFAVICON_TEXTDOMAIN),
        'frontendGIF' => __('GIF',AIOFAVICON_TEXTDOMAIN),
        'frontendPNG' => __('PNG',AIOFAVICON_TEXTDOMAIN),
        'frontendApple' => __('Apple Touch Icon',AIOFAVICON_TEXTDOMAIN)
      );

      //mapping of favicon types to translatable Strings
      $this->aioFaviconBackendMap = array(
        'backendICO' => __('ICO',AIOFAVICON_TEXTDOMAIN),
        'backendGIF' => __('GIF',AIOFAVICON_TEXTDOMAIN),
        'backendPNG' => __('PNG',AIOFAVICON_TEXTDOMAIN),
        'backendApple' => __('Apple Touch Icon',AIOFAVICON_TEXTDOMAIN)

All that I have done is added an extra _ to each line (changing each _ to _e would also work, but I thought adding another _ looked easier to the eye when checking over the code in the future), which fixes the problem and will stop displaying the warnings ??

I just update my all in one fav icon plugin too and had the same warnings, but its a simple fix and just a little mistake in the coding of that file.

Simply head to the file in the warning and change the following lines of code from:

'frontendICO' => _('ICO',AIOFAVICON_TEXTDOMAIN),
        'frontendGIF' => _('GIF',AIOFAVICON_TEXTDOMAIN),
        'frontendPNG' => _('PNG',AIOFAVICON_TEXTDOMAIN),
        'frontendApple' => _('Apple Touch Icon',AIOFAVICON_TEXTDOMAIN)
      );

      //mapping of favicon types to translatable Strings
      $this->aioFaviconBackendMap = array(
        'backendICO' => _('ICO',AIOFAVICON_TEXTDOMAIN),
        'backendGIF' => _('GIF',AIOFAVICON_TEXTDOMAIN),
        'backendPNG' => _('PNG',AIOFAVICON_TEXTDOMAIN),
        'backendApple' => _('Apple Touch Icon',AIOFAVICON_TEXTDOMAIN)

Change to:

'frontendICO' => __('ICO',AIOFAVICON_TEXTDOMAIN),
        'frontendGIF' => __('GIF',AIOFAVICON_TEXTDOMAIN),
        'frontendPNG' => __('PNG',AIOFAVICON_TEXTDOMAIN),
        'frontendApple' => __('Apple Touch Icon',AIOFAVICON_TEXTDOMAIN)
      );

      //mapping of favicon types to translatable Strings
      $this->aioFaviconBackendMap = array(
        'backendICO' => __('ICO',AIOFAVICON_TEXTDOMAIN),
        'backendGIF' => __('GIF',AIOFAVICON_TEXTDOMAIN),
        'backendPNG' => __('PNG',AIOFAVICON_TEXTDOMAIN),
        'backendApple' => __('Apple Touch Icon',AIOFAVICON_TEXTDOMAIN)

All that I have done is added an extra _ to each line (changing each _ to _e would also work, but I thought adding another _ looked easier to the eye when checking over the code in the future), which fixes the problem and will stop displaying the warnings ??

I just update my all in one fav icon plugin too and had the same warnings, but its a simple fix and just a little mistake in the coding of that file.

Simply head to the file in the warning and change the following lines of code from:

'frontendICO' => _('ICO',AIOFAVICON_TEXTDOMAIN),
        'frontendGIF' => _('GIF',AIOFAVICON_TEXTDOMAIN),
        'frontendPNG' => _('PNG',AIOFAVICON_TEXTDOMAIN),
        'frontendApple' => _('Apple Touch Icon',AIOFAVICON_TEXTDOMAIN)
      );

      //mapping of favicon types to translatable Strings
      $this->aioFaviconBackendMap = array(
        'backendICO' => _('ICO',AIOFAVICON_TEXTDOMAIN),
        'backendGIF' => _('GIF',AIOFAVICON_TEXTDOMAIN),
        'backendPNG' => _('PNG',AIOFAVICON_TEXTDOMAIN),
        'backendApple' => _('Apple Touch Icon',AIOFAVICON_TEXTDOMAIN)

Change to:

'frontendICO' => __('ICO',AIOFAVICON_TEXTDOMAIN),
        'frontendGIF' => __('GIF',AIOFAVICON_TEXTDOMAIN),
        'frontendPNG' => __('PNG',AIOFAVICON_TEXTDOMAIN),
        'frontendApple' => __('Apple Touch Icon',AIOFAVICON_TEXTDOMAIN)
      );

      //mapping of favicon types to translatable Strings
      $this->aioFaviconBackendMap = array(
        'backendICO' => __('ICO',AIOFAVICON_TEXTDOMAIN),
        'backendGIF' => __('GIF',AIOFAVICON_TEXTDOMAIN),
        'backendPNG' => __('PNG',AIOFAVICON_TEXTDOMAIN),
        'backendApple' => __('Apple Touch Icon',AIOFAVICON_TEXTDOMAIN)

All that I have done is added an extra _ to each line, which fixes the problem and will stop displaying the warnings ??

Thanks dude, its working like a charm ??

*EDIT*
Scrap my last question (deleted it), I didn’t notice the option “Scale large content down to fit in the browser viewport.”

Thanks for all the help and the link to the developer version, its working much better now and making my image look a lot sexier then opening in a new window/tab lol ??

You earned a 5 star rating from me for the plugin and support A++

Thanks RavanH, I will give that development version a try because it could be a number of security plugins I’m running that could be the cause of this not working by the sounds of it, and ofc I don’t want to disable those at the risk of making my site less secure.

yer sure thing mate, thanks for the reply, will head over to the support page now ??