rollbrettfahrer77
Forum Replies Created
-
Forum: Plugins
In reply to: [WooCommerce] Checkout issue in IE8 (v. 2.1.5)Deactivated all other plugins one-by-one, trying several things from older threads regarding the spinning wheel of death on checkout, nothing worked so it really seems to be a new issue with 2.1.5
Forum: Plugins
In reply to: [WooCommerce] Checkout issue in IE8 (v. 2.1.5)Wow, thank you for pointing this one out. I have the same issue, but still no clue why.
Forum: Plugins
In reply to: [WooCommerce] Show empty categories not workingMy solution for showing empty product categories was even more of a ugly hack, but maybe a helpful idea for somebody:
– make a dummy product (not searchable) in the category
– do a redirect permanent in your htaccess for the category’s url to another page. Maybe for the product itself a redirect would make sense, too.Only problem is, it throws you out of your shop path then.
Forum: Plugins
In reply to: [WooCommerce German (de_DE)] update to 3.1.0 -> emails work no moreWith Woocommerce 2.1.0, emails work again. Sorry for panicking.
Forum: Plugins
In reply to: [WooCommerce German (de_DE)] update to 3.1.0 -> emails work no moreOk maybe it’s because I haven’t updated Woocommerce itself yet from 2.0.20 to 2.1.0. Will do that now.
Forum: Plugins
In reply to: [WP Fastest Cache] does it work?Maybe it’s this:
Some hosts do not set the variable {DOCUMENT_ROOT} accurately.
I replaced this in the .htaccess with my absolut path and then it worked.
Forum: Plugins
In reply to: [WP Super Cache] Clear all cache after editing postSeveral people including me seem to have the problem that, no matter if checkbox “Clear all cache files when a post or page is published or updated” is set, all the cache is cleared.
This would be a great plugin for us, but as we run a woocommerce shop with frequently updated product stock, it’s totally useless for us as long as all cache is cleared any 10 minutes.
I tried like, any configuration of the plugin.
We are running 3.8.1 on PHP 5.4.9, same problem with 5.2.17
This is a part of my log, starting with editing a random post.
The WP installation is located in a subdirectory.
Same as in alex1305s log, I noticed a path with the string //page in it, although we do not use this in our permalinks.
07:50:03 /blog/wp-admin/post.php wp_cache_post_edit: Clearing cache for post 3595 on post edit. 07:50:03 /blog/wp-admin/post.php supercache dir: /kunden/12345_6789/webseiten/blog/wp-content/cache/supercache/www.mydomain.com/blog/test-news-mm/ 07:50:03 /blog/wp-admin/post.php wp_cache_post_id_gc post_id: 3595 https://www.mydomain.com/blog/test-news-mm/ clearing cache in /kunden/12345_6789/webseiten/blog/wp-content/cache/supercache/www.mydomain.com/blog/test-news-mm/. 07:50:03 /blog/wp-admin/post.php wp_cache_post_id_gc clearing cache in /kunden/12345_6789/webseiten/blog/wp-content/cache/supercache/www.mydomain.com/blog/test-news-mm//page/. 07:50:03 /blog/wp-admin/post.php wp_cache_post_id_gc clearing cache in /kunden/12345_6789/webseiten/blog/wp-content/cache/supercache/www.mydomain.com/blog//page/. 07:50:03 /blog/wp-admin/post.php Post change: deleting cache files in /kunden/12345_6789/webseiten/blog/wp-content/cache/supercache/www.mydomain.com/blog/ 07:50:03 /blog/wp-admin/post.php prune_super_cache: wp_cache_rebuild_or_delete( /kunden/12345_6789/webseiten/blog/wp-content/cache/supercache/www.mydomain.com/blog/index.html ) 07:50:03 /blog/wp-admin/post.php rebuild_or_gc: rename to /kunden/12345_6789/webseiten/blog/wp-content/cache/supercache/www.mydomain.com/blog/index.html.needs-rebuild 07:50:03 /blog/wp-admin/post.php Post change: deleting page_on_front and page_for_posts pages. 07:50:03 /blog/wp-admin/post.php Post change: page_on_front 389 07:50:03 /blog/wp-admin/post.php supercache dir: /kunden/12345_6789/webseiten/blog/wp-content/cache/supercache/www.mydomain.com/blog/ 07:50:03 /blog/wp-admin/post.php wp_cache_post_id_gc post_id: 389 https://www.mydomain.com/blog/ clearing cache in /kunden/12345_6789/webseiten/blog/wp-content/cache/supercache/www.mydomain.com/blog/. 07:50:03 /blog/wp-admin/post.php wp_cache_post_id_gc clearing cached index files in /kunden/12345_6789/webseiten/blog/wp-content/cache/supercache/www.mydomain.com/blog/. 07:50:03 /blog/wp-admin/post.php prune_super_cache: wp_cache_rebuild_or_delete( /kunden/12345_6789/webseiten/blog/wp-content/cache/supercache/www.mydomain.com/blog/ps3-paket-gran-turismo-6-wireless-dualshock-controller-nur-66-euro/index.html ) 07:50:03 /blog/wp-admin/post.php rebuild_or_gc: rename to /kunden/12345_6789/webseiten/blog/wp-content/cache/supercache/www.mydomain.com/blog/ps3-paket-gran-turismo-6-wireless-dualshock-controller-nur-66-euro/index.html.needs-rebuild
Forum: Plugins
In reply to: [Cachify] Blog in subdir – what to put in subdir/.htaccess?before you ask – yes I did replace /wordpress/ with /blog/
and the rest of my /blog/.htaccess is
<IfModule mod_expires.c> ExpiresActive on ExpiresDefault "access plus 1 month" ExpiresByType application/javascript "access plus 1 year" ExpiresByType image/x-ico "access plus 1 year" ExpiresByType image/jpg "access plus 14 days" ExpiresByType image/jpeg "access plus 14 days" ExpiresByType image/gif "access plus 14 days" ExpiresByType image/png "access plus 14 days" ExpiresByType text/css "access plus 14 days" </IfModule> # BEGIN WordPress <IfModule mod_rewrite.c> RewriteEngine On RewriteBase /blog/ RewriteRule ^index\.php$ - [L] RewriteCond %{REQUEST_FILENAME} !-f RewriteCond %{REQUEST_FILENAME} !-d RewriteRule . /blog/index.php [L] </IfModule> # END WordPress
Forum: Plugins
In reply to: [ABASE] Hidden/Appearing Query RowsKind of solved this by adding limit=”1″ on the results page.
Forum: Plugins
In reply to: [WooCommerce Poor Guys Swiss Knife] Parse error when activatingJuhu, Installation klappt jetzt, nun geht’s an die Funktionalit?t ??
PHP Version 5.2.17 System Linux everell.ispgateway.de 2.6.32.53-grsec-pvops-xen-x64 #4 SMP Wed May 30 15:30:38 CEST 2012 x86_64 Build Date May 9 2012 09:49:15 Configure Command './configure' '--with-mysql=/usr/local/mysql' '--with-config-file-path=/usr/local/php5' '--with-mysqli' '--with-openssl' '--with-gd' '--disable-force-cgi-redirect' '--enable-discard-path' '--enable-ftp' '--enable-calendar' '--with-libxml-dir' '--with-jpeg-dir=../jpeg-6b/' '--with-ttf' '--with-freetype-dir=/usr/lib' '--with-gettext' '--with-zlib-dir=../zlib-1.1.3/' '--with-png-dir=../libpng-1.0.6/' '--with-gdbm' '--with-ndbm' '--enable-dba' '--enable-wddx' '--enable-bcmath' '--enable-exif' '--with-curl' '--enable-dbase' '--enable-inline-optimization' '--with-gnu-ld' '--with-zlib' '--with-mcrypt=' '--with-xsl' '--enable-wddx' '--with-mhash' '--with-pgsql' '--with-bz2' '--with-pdo-mysql=/usr' '--with-iconv' '--enable-soap' '--with-imap=/usr/local/imap-2007e' '--with-imap-ssl=/usr/local/imap-2007e' '--enable-mbstring' Server API CGI Virtual Directory Support disabled Configuration File (php.ini) Path /usr/local/php5 Loaded Configuration File /usr/local/php5-SECURE/php.ini Scan this dir for additional .ini files (none) additional .ini files parsed (none) PHP API 20041225 PHP Extension 20060613 Zend Extension 220060519 Debug Build no Thread Safety disabled Zend Memory Manager enabled IPv6 Support enabled Registered PHP Streams https, ftps, compress.zlib, compress.bzip2, php, file, data, http, ftp Registered Stream Socket Transports tcp, udp, unix, udg, ssl, sslv3, sslv2, tls Registered Stream Filters zlib.*, bzip2.*, convert.iconv.*, string.rot13, string.toupper, string.tolower, string.strip_tags, convert.*, consumed
Forum: Plugins
In reply to: [WooCommerce Poor Guys Swiss Knife] Parse error when activatingDanke fürs schnelle Feedback, leider habe ich mit der 1.4.1. den gleichen Fehler, allerdings auf Zeile 679
WordPress 3.8, Woocommerce 2.0.20
English: same bug, different line ??
Forum: Plugins
In reply to: [ABASE] Hidden/Appearing Query RowsYou could output the results on an extra page by adding an url parameter in form=”…”
[abase form="1,search,/results" table="employees" columns="first_name,last_name$Search Employees" elements="first_name,last_name"]
then on the /results page
[abase table="employees" columns="first_name,last_name" ack="green"]
BUT the whole data set would still be viewable to the clever user when he goes directly to /results.
Any ideas for a better solution?