Forum Replies Created

Viewing 15 replies - 61 through 75 (of 98 total)
  • Thread Starter 3Lancer

    (@3lancer)

    @achi_nr – PHP XSL Module is something your Host server would provide for your PHP. Depending on your Web Server, check under your cPanel, root access (if available), or ask them to install it for you.

    Thread Starter 3Lancer

    (@3lancer)

    You need to recreate that ‘.htaccess’ file or disable it from automatically being update by various different plugins.

    It’s normally just a spacing, or missing of the end comment, etc, which can throw it off.

    For example:
    # BEGIN WordPress
    (all this content is what wordpress generates)
    # END WordPress

    Then when other plugins come along such as security and this caching, they will may place more above.

    # BEGIN W3TC Browser Cache
    (caching here)
    # END W3TC Browser Cache

    etc… they all have to match perfectly.

    Make a backup of a working ‘.htaccess’.

    You might have to disable other plugins from accessing your ‘.htacccess’ – set them all to manual for now.

    Depending on your visitors. Delete the one on the server, create an empty ‘.htaccess’ replacement, then under the WordPress Admin quickly update your permalinks (simply resave it under your options). WordPress will then full back in the ‘.htaccess’.

    Once WordPress has done it’s chuck, then do the plugins that have also added content into the ‘.htaccess’ one by one – testing each time. Or manually copy and paste it into the correct locations.

    In my case though, the root cause was due to running of large cronjobs at that point of time.

    For WordPress cronjobs – I moved them to real server cronjobs, this tends to work a lot better and provide less overlapping/conflict for large jobs that take time. This is however more complex and if WordPress Plugins also have their own cronjobs, they need to be setup separately.

    If you wanted to do that too under ‘wp-config.php’:
    define(‘DISABLE_WP_CRON’, true);

    Then on your server recreate the cronjob, for example:
    */15 * * * * cd /wordpress/location/ && /usr/bin/php /wordpress/location/wp-cron.php >/dev/null 2>&1

    This is basically saying each 15 minutes go to the WordPress directory and run the WordPress CronJob ‘wp-cron.php’ on a Linux server. If your unsure about Cron Jobs, I wouldn’t suggest trying it, they need to be setup correctly or your WordPress won’t do schedule posts, htaccess updates, etc.

    This still occurs even in Version 2.0.66.17.

    Seems to be high memory usage, when using this plugin with a large collection of others, such as NextGEN Public Uploader, Justified Image Grids, etc.

    ‘ERROR 500 – INTERNAL SERVER ERROR’

    Occurs mostly via the admin backend – gallery settings/options or management pages of this plugin.

    Pretty sure it’s memory related or due to overlapping plugins. Increasing WordPress WP_MEMORY_LIMIT to 256MB didn’t help. However, deactivating other plugins such as NextGEN Public Uploader, helps a lot.

    Thread Starter 3Lancer

    (@3lancer)

    This just turned out to be a memory restriction issue on the server, fixed. Nothing wrong with the plugins working together.

    Thread Starter 3Lancer

    (@3lancer)

    Updating your WordPress to the latest 3.9.2 might also help address this issue: https://www.ads-software.com/news/2014/08/wordpress-3-9-2/

    I asked this a couple weeks ago, is this what your after as well?
    https://www.ads-software.com/support/topic/product-featured-images-thumbnail-full

    Still no solution as of yet? Will update if I find anything.

    Thread Starter 3Lancer

    (@3lancer)

    Many thanks Arnee, version 4.0.5 appears to of fixed this issue nicely. Cheers!

    This is due to a mislocation of where it’s trying to find the admin.css…

    If you look at the WordPress ‘widget.php’ page source code, it’s currently attempting to link the CSS location:
    /wp-content/plugins/recent-posts-widget-extended/assets/css/rpwe-admin.css

    However, the files correct location is actually here now:
    /wp-content/plugins/recent-posts-widget-extended/includes/admin.css

    To fix…

    You are required to edit the ‘wp-content/plugins/recent-posts-widget-extended/rpwe.php’ file.

    At around line 153, change the folder name – ‘assets’ to ‘includes’:

    /* Set the constant path to the assets directory. */
    define( 'RPWE_ASSETS', RPWE_URI . trailingslashit( 'includes' ) );

    Scroll down to the admin style function and at around line 233, correct the ‘css/rpwe-admin.css’ name and location to just ‘/admin.css’:

    /* Loads the widget style. */
    wp_enqueue_style( 'rpwe-admin-style', trailingslashit( RPWE_ASSETS ) . '/admin.css', null, null );

    Make sure you have a backup, save and replace the file. Reload the page. Check that the CSS isn’t 404 anymore. Dialog panel should now be styled correctly. Solved.

    Thread Starter 3Lancer

    (@3lancer)

    I’ve already resolved this…

    For anyone else experiencing it:

    It’s due to the caching plugin – W3 Total Cache
    Under that is a section for cache priming.

    When enabled and set as default, the XML path to the sitemap lookup to do this pre-caching is:
    sitemap_index.xml

    You just need to ensure it’s set correctly to:
    sitemap.xml

    Then resave it, easy fix (was just looking in the wrong place).

    Thread Starter 3Lancer

    (@3lancer)

    Fixed – was due to another plugin being limited…

    For others:

    Check limit of ‘max_input_vars’ on the server php.ini

    Increase PHP Memory from WordPress default 40MB (or 64MB) to recommended 128MB if required for support of WooCommerce, other certain plugins and/or high visitor traffic – under your wp-config.php:
    define(‘WP_MEMORY_LIMIT’, ‘128M’);

    Disable other plugins / cronjobs if possible to narrow down the issue.

    WooCommerce and Amazon plugin was causing issues and this was just a side effect of it, WordPress itself overwriting the ‘.htaccess’ file in the wrong location.

    Thread Starter 3Lancer

    (@3lancer)

    Fixed – was due to another plugin being limited…

    For others:

    Check limit of ‘max_input_vars’ on the server php.ini

    Increase PHP Memory from WordPress default 40MB (or 64MB) to recommended 128MB if required for support of WooCommerce, other certain plugins and/or high visitor traffic – under your wp-config.php:
    define('WP_MEMORY_LIMIT', '128M');

    Disable other plugins / cronjobs if possible to narrow down the issue.

    WooCommerce and Amazon plugin was causing issues and this was just a side effect of it, WordPress itself overwriting the ‘.htaccess’ file in the wrong location.

    Thread Starter 3Lancer

    (@3lancer)

    Original iTheme Security ‘.htaccess’ it’s overwriting appears valid to me:

    # BEGIN iThemes Security
    	# BEGIN Ban Users
    		# Begin HackRepair.com Blacklist
    		RewriteEngine on
    		RewriteCond %{HTTP_USER_AGENT} ^[Ww]eb[Bb]andit [NC,OR]
    		RewriteCond %{HTTP_USER_AGENT} ^binlar [NC,OR]
    		RewriteCond %{HTTP_USER_AGENT} ^BlackWidow [NC,OR]
    		RewriteCond %{HTTP_USER_AGENT} ^Bolt\ 0 [NC,OR]
    		RewriteCond %{HTTP_USER_AGENT} ^Bot\ mailto:craftbot\@yahoo\.com [NC,OR]
    		RewriteCond %{HTTP_USER_AGENT} ^casper [NC,OR]
    		RewriteCond %{HTTP_USER_AGENT} ^ChinaClaw [NC,OR]
    		RewriteCond %{HTTP_USER_AGENT} ^cmsworldmap [NC,OR]
    		RewriteCond %{HTTP_USER_AGENT} ^comodo [NC,OR]
    		RewriteCond %{HTTP_USER_AGENT} ^Custo [NC,OR]
    		RewriteCond %{HTTP_USER_AGENT} ^Default\ Browser\ 0 [NC,OR]
    		RewriteCond %{HTTP_USER_AGENT} ^diavol [NC,OR]
    		RewriteCond %{HTTP_USER_AGENT} ^DIIbot [NC,OR]
    		RewriteCond %{HTTP_USER_AGENT} ^DISCo [NC,OR]
    		RewriteCond %{HTTP_USER_AGENT} ^dotbot [NC,OR]
    		RewriteCond %{HTTP_USER_AGENT} ^Download\ Demon [NC,OR]
    		RewriteCond %{HTTP_USER_AGENT} ^eCatch [NC,OR]
    		RewriteCond %{HTTP_USER_AGENT} ^EirGrabber [NC,OR]
    		RewriteCond %{HTTP_USER_AGENT} ^EmailCollector [NC,OR]
    		RewriteCond %{HTTP_USER_AGENT} ^EmailSiphon [NC,OR]
    		RewriteCond %{HTTP_USER_AGENT} ^EmailWolf [NC,OR]
    		RewriteCond %{HTTP_USER_AGENT} ^Express\ WebPictures [NC,OR]
    		RewriteCond %{HTTP_USER_AGENT} ^ExtractorPro [NC,OR]
    		RewriteCond %{HTTP_USER_AGENT} ^EyeNetIE [NC,OR]
    		RewriteCond %{HTTP_USER_AGENT} ^feedfinder [NC,OR]
    		RewriteCond %{HTTP_USER_AGENT} ^FlashGet [NC,OR]
    		RewriteCond %{HTTP_USER_AGENT} ^flicky [NC,OR]
    		RewriteCond %{HTTP_USER_AGENT} ^GetRight [NC,OR]
    		RewriteCond %{HTTP_USER_AGENT} ^GetWeb! [NC,OR]
    		RewriteCond %{HTTP_USER_AGENT} ^Go-Ahead-Got-It [NC,OR]
    		RewriteCond %{HTTP_USER_AGENT} ^Go!Zilla [NC,OR]
    		RewriteCond %{HTTP_USER_AGENT} ^GrabNet [NC,OR]
    		RewriteCond %{HTTP_USER_AGENT} ^Grafula [NC,OR]
    		RewriteCond %{HTTP_USER_AGENT} ^HMView [NC,OR]
    		RewriteCond %{HTTP_USER_AGENT} ^ia_archiver [NC,OR]
    		RewriteCond %{HTTP_USER_AGENT} ^Image\ Stripper [NC,OR]
    		RewriteCond %{HTTP_USER_AGENT} ^Image\ Sucker [NC,OR]
    		RewriteCond %{HTTP_USER_AGENT} ^InterGET [NC,OR]
    		RewriteCond %{HTTP_USER_AGENT} ^Internet\ Ninja [NC,OR]
    		RewriteCond %{HTTP_USER_AGENT} ^InternetSeer\.com [NC,OR]
    		RewriteCond %{HTTP_USER_AGENT} ^jakarta [NC,OR]
    		RewriteCond %{HTTP_USER_AGENT} ^Java [NC,OR]
    		RewriteCond %{HTTP_USER_AGENT} ^JetCar [NC,OR]
    		RewriteCond %{HTTP_USER_AGENT} ^JOC\ Web\ Spider [NC,OR]
    		RewriteCond %{HTTP_USER_AGENT} ^kmccrew [NC,OR]
    		RewriteCond %{HTTP_USER_AGENT} ^larbin [NC,OR]
    		RewriteCond %{HTTP_USER_AGENT} ^LeechFTP [NC,OR]
    		RewriteCond %{HTTP_USER_AGENT} ^Mass\ Downloader [NC,OR]
    		RewriteCond %{HTTP_USER_AGENT} ^Maxthon$ [NC,OR]
    		RewriteCond %{HTTP_USER_AGENT} ^microsoft\.url [NC,OR]
    		RewriteCond %{HTTP_USER_AGENT} ^MIDown\ tool [NC,OR]
    		RewriteCond %{HTTP_USER_AGENT} ^Mister\ PiX [NC,OR]
    		RewriteCond %{HTTP_USER_AGENT} ^Mozilla\.*Indy [NC,OR]
    		RewriteCond %{HTTP_USER_AGENT} ^Mozilla\.*NEWT [NC,OR]
    		RewriteCond %{HTTP_USER_AGENT} ^MSFrontPage [NC,OR]
    		RewriteCond %{HTTP_USER_AGENT} ^Navroad [NC,OR]
    		RewriteCond %{HTTP_USER_AGENT} ^NearSite [NC,OR]
    		RewriteCond %{HTTP_USER_AGENT} ^Net\ Vampire [NC,OR]
    		RewriteCond %{HTTP_USER_AGENT} ^NetAnts [NC,OR]
    		RewriteCond %{HTTP_USER_AGENT} ^NetSpider [NC,OR]
    		RewriteCond %{HTTP_USER_AGENT} ^NetZIP [NC,OR]
    		RewriteCond %{HTTP_USER_AGENT} ^nutch [NC,OR]
    		RewriteCond %{HTTP_USER_AGENT} ^Octopus [NC,OR]
    		RewriteCond %{HTTP_USER_AGENT} ^Offline\ Explorer [NC,OR]
    		RewriteCond %{HTTP_USER_AGENT} ^Offline\ Navigator [NC,OR]
    		RewriteCond %{HTTP_USER_AGENT} ^PageGrabber [NC,OR]
    		RewriteCond %{HTTP_USER_AGENT} ^Papa\ Foto [NC,OR]
    		RewriteCond %{HTTP_USER_AGENT} ^pavuk [NC,OR]
    		RewriteCond %{HTTP_USER_AGENT} ^pcBrowser [NC,OR]
    		RewriteCond %{HTTP_USER_AGENT} ^PeoplePal [NC,OR]
    		RewriteCond %{HTTP_USER_AGENT} ^planetwork [NC,OR]
    		RewriteCond %{HTTP_USER_AGENT} ^psbot [NC,OR]
    		RewriteCond %{HTTP_USER_AGENT} ^purebot [NC,OR]
    		RewriteCond %{HTTP_USER_AGENT} ^pycurl [NC,OR]
    		RewriteCond %{HTTP_USER_AGENT} ^RealDownload [NC,OR]
    		RewriteCond %{HTTP_USER_AGENT} ^ReGet [NC,OR]
    		RewriteCond %{HTTP_USER_AGENT} ^Rippers\ 0 [NC,OR]
    		RewriteCond %{HTTP_USER_AGENT} ^SeaMonkey$ [NC,OR]
    		RewriteCond %{HTTP_USER_AGENT} ^sitecheck\.internetseer\.com [NC,OR]
    		RewriteCond %{HTTP_USER_AGENT} ^SiteSnagger [NC,OR]
    		RewriteCond %{HTTP_USER_AGENT} ^skygrid [NC,OR]
    		RewriteCond %{HTTP_USER_AGENT} ^SmartDownload [NC,OR]
    		RewriteCond %{HTTP_USER_AGENT} ^sucker [NC,OR]
    		RewriteCond %{HTTP_USER_AGENT} ^SuperBot [NC,OR]
    		RewriteCond %{HTTP_USER_AGENT} ^SuperHTTP [NC,OR]
    		RewriteCond %{HTTP_USER_AGENT} ^Surfbot [NC,OR]
    		RewriteCond %{HTTP_USER_AGENT} ^tAkeOut [NC,OR]
    		RewriteCond %{HTTP_USER_AGENT} ^Teleport\ Pro [NC,OR]
    		RewriteCond %{HTTP_USER_AGENT} ^Toata\ dragostea\ mea\ pentru\ diavola [NC,OR]
    		RewriteCond %{HTTP_USER_AGENT} ^turnit [NC,OR]
    		RewriteCond %{HTTP_USER_AGENT} ^vikspider [NC,OR]
    		RewriteCond %{HTTP_USER_AGENT} ^VoidEYE [NC,OR]
    		RewriteCond %{HTTP_USER_AGENT} ^Web\ Image\ Collector [NC,OR]
    		RewriteCond %{HTTP_USER_AGENT} ^Web\ Sucker [NC,OR]
    		RewriteCond %{HTTP_USER_AGENT} ^WebAuto [NC,OR]
    		RewriteCond %{HTTP_USER_AGENT} ^WebCopier [NC,OR]
    		RewriteCond %{HTTP_USER_AGENT} ^WebFetch [NC,OR]
    		RewriteCond %{HTTP_USER_AGENT} ^WebGo\ IS [NC,OR]
    		RewriteCond %{HTTP_USER_AGENT} ^WebLeacher [NC,OR]
    		RewriteCond %{HTTP_USER_AGENT} ^WebReaper [NC,OR]
    		RewriteCond %{HTTP_USER_AGENT} ^WebSauger [NC,OR]
    		RewriteCond %{HTTP_USER_AGENT} ^WPScan [NC,OR]
    		RewriteCond %{HTTP_USER_AGENT} ^Website\ eXtractor [NC,OR]
    		RewriteCond %{HTTP_USER_AGENT} ^Website\ Quester [NC,OR]
    		RewriteCond %{HTTP_USER_AGENT} ^WebStripper [NC,OR]
    		RewriteCond %{HTTP_USER_AGENT} ^WebWhacker [NC,OR]
    		RewriteCond %{HTTP_USER_AGENT} ^WebZIP [NC,OR]
    		RewriteCond %{HTTP_USER_AGENT} ^Wget [NC,OR]
    		RewriteCond %{HTTP_USER_AGENT} ^Widow [NC,OR]
    		RewriteCond %{HTTP_USER_AGENT} ^WWW-Mechanize [NC,OR]
    		RewriteCond %{HTTP_USER_AGENT} ^WWWOFFLE [NC,OR]
    		RewriteCond %{HTTP_USER_AGENT} ^Xaldon\ WebSpider [NC,OR]
    		RewriteCond %{HTTP_USER_AGENT} ^Zeus [NC,OR]
    		RewriteCond %{HTTP_USER_AGENT} ^zmeu [NC,OR]
    		RewriteCond %{HTTP_USER_AGENT} ^CazoodleBot [NC,OR]
    		RewriteCond %{HTTP_USER_AGENT} ^discobot [NC,OR]
    		RewriteCond %{HTTP_USER_AGENT} ^ecxi [NC,OR]
    		RewriteCond %{HTTP_USER_AGENT} ^GT::WWW [NC,OR]
    		RewriteCond %{HTTP_USER_AGENT} ^heritrix [NC,OR]
    		RewriteCond %{HTTP_USER_AGENT} ^HTTP::Lite [NC,OR]
    		RewriteCond %{HTTP_USER_AGENT} ^HTTrack [NC,OR]
    		RewriteCond %{HTTP_USER_AGENT} ^ia_archiver [NC,OR]
    		RewriteCond %{HTTP_USER_AGENT} ^id-search [NC,OR]
    		RewriteCond %{HTTP_USER_AGENT} ^id-search\.org [NC,OR]
    		RewriteCond %{HTTP_USER_AGENT} ^IDBot [NC,OR]
    		RewriteCond %{HTTP_USER_AGENT} ^Indy\ Library [NC,OR]
    		RewriteCond %{HTTP_USER_AGENT} ^IRLbot [NC,OR]
    		RewriteCond %{HTTP_USER_AGENT} ^ISC\ Systems\ iRc\ Search\ 2\.1 [NC,OR]
    		RewriteCond %{HTTP_USER_AGENT} ^LinksManager.com_bot [NC,OR]
    		RewriteCond %{HTTP_USER_AGENT} ^linkwalker [NC,OR]
    		RewriteCond %{HTTP_USER_AGENT} ^lwp-trivial [NC,OR]
    		RewriteCond %{HTTP_USER_AGENT} ^MFC_Tear_Sample [NC,OR]
    		RewriteCond %{HTTP_USER_AGENT} ^Microsoft\ URL\ Control [NC,OR]
    		RewriteCond %{HTTP_USER_AGENT} ^Missigua\ Locator [NC,OR]
    		RewriteCond %{HTTP_USER_AGENT} ^panscient.com [NC,OR]
    		RewriteCond %{HTTP_USER_AGENT} ^PECL::HTTP [NC,OR]
    		RewriteCond %{HTTP_USER_AGENT} ^PHPCrawl [NC,OR]
    		RewriteCond %{HTTP_USER_AGENT} ^PleaseCrawl [NC,OR]
    		RewriteCond %{HTTP_USER_AGENT} ^SBIder [NC,OR]
    		RewriteCond %{HTTP_USER_AGENT} ^Snoopy [NC,OR]
    		RewriteCond %{HTTP_USER_AGENT} ^Steeler [NC,OR]
    		RewriteCond %{HTTP_USER_AGENT} ^URI::Fetch [NC,OR]
    		RewriteCond %{HTTP_USER_AGENT} ^urllib [NC,OR]
    		RewriteCond %{HTTP_USER_AGENT} ^User-Agent [NC,OR]
    		RewriteCond %{HTTP_USER_AGENT} ^Web\ Sucker [NC,OR]
    		RewriteCond %{HTTP_USER_AGENT} ^webalta [NC,OR]
    		RewriteCond %{HTTP_USER_AGENT} ^WebCollage [NC,OR]
    		RewriteCond %{HTTP_USER_AGENT} ^Wells\ Search\ II [NC,OR]
    		RewriteCond %{HTTP_USER_AGENT} ^WEP\ Search [NC,OR]
    		RewriteCond %{HTTP_USER_AGENT} ^zermelo [NC,OR]
    		RewriteCond %{HTTP_USER_AGENT} ^ZyBorg [NC]
    		RewriteRule ^.* - [F]
    
    	# END Ban Users

    As you see, it’s cutting into it and merely dumping itself over the top – cutting the content slightly.

    Had to hack this plugin’s ‘qtranslate_core.php’ file at line 455.

    // WordPress 3.9 Fix
    //return $before.strftime($format, $date).$after;
    return strftime($format, $date).$after;

    It’s just a matter of removing that ‘$before.’ which causes all sorts of issues in regards to getting content before the date stamp.

    Then with the ‘qtranslate.php’ just find and update the allowed WordPress version to the latest.

    define('QT_SUPPORTED_WP_VERSION', '3.9');

    I haven’t run into any issues so far doing this, but best to test for yourself and have backups incase.

    EDIT: Backend Visual Editor will still be broken with this fix and some more tweaking might be required…

    What’s mqtranslate like compared to this one? Has the original developer given up on support so someone else tried to take over or are they actually different?

    Thread Starter 3Lancer

    (@3lancer)

    Resolved it myself, closing…

    Thread Starter 3Lancer

    (@3lancer)

    Nevermind, I have tracked it down to the QTranslate Plugin being incompatible – used for multiple languages.

    For anyone else using QTranslate Plugin and wanting a solution…

    Had to hack it’s ‘qtranslate_core.php’ file at line 455.

    // WordPress 3.9 Fix
    //return $before.strftime($format, $date).$after;
    return strftime($format, $date).$after;

    It’s just a matter of removing that ‘$before.’ which causes all sorts of issues in regards to getting content before the date stamp.

Viewing 15 replies - 61 through 75 (of 98 total)