Rynald0s

Session Shredder is a production-grade, rule-based session cleanup plugin for WooCommerce 10.3+.
WooCommerce 10.3 introduces experimental guest session storage and auto-pruning. Session Shredder builds directly on this already available foundation and adds behavior-based heuristics that predict which sessions are zombies (safe to prune) versus keepers (should be retained).
Highlights
– Heuristic pruning – Uses anonymized features (session age, pageviews, cart value, etc.) and conservative rules to identify low-value sessions. 
– Configurable rules & thresholds – Tune base age, hard timeout, bounce detection, and cart-protection rules from a dedicated WooCommerce settings screen. 
– Safe thresholds – Only considers sessions past a base age window and is biased towards keeping anything that shows meaningful activity or cart value. 
– Robust behavior – Even if tracking data is sparse, a conservative rule-based strategy kicks in (e.g. hard 72h timeout, bounces with no cart value). 
– Privacy-first – No PII is stored. Session IDs and countries are hashed; only coarse behavioral data is used. 
– Native Woo 10.3 integration – Reads from the WooCommerce session table (supports both legacy and new tables) and plays nicely with the core experimental pruning. 
– HPOS compatible – Declares compatibility with WooCommerce High-Performance Order Storage (custom order tables) and never touches orders, only session data. 
– Admin dashboard – Under WooCommerce → Session Shredder you get active sessions, pruned counts, a Chart.js visualization of active & pruned sessions per run, and a compact “Recent runs” summary. 
– Logging & observability – Uses <code>wc_get_logger()</code> for info/error logging; integrates cleanly with existing WooCommerce logs.
Session Shredder is structured for real-world stores and designed as a companion to WooCommerce’s experimental guest session engine. It stays fully rule-based out of the box, but developers can extend it via hooks if they ever want to plug in external scoring services or AI endpoints.
Why not rely only on the WooCommerce experimental pruning?
– Core experimental pruning is largely age-based and opaque. 
– Session Shredder adds behavior-aware rules (pageviews, cart value, bounce flag) on top of age. 
– You get a dry-run mode to analyze impact before deleting anything. 
– The dashboard gives you visibility into how many sessions were pruned per run and how many sessions remained active. 
– WP-CLI commands let you script and automate analyze/prune runs. 
– It works alongside WooCommerce experimental guest sessions and HPOS rather than replacing them: Woo can still prune based on its own rules, while Session Shredder adds a tunable, rule-based layer with better reporting.
<h3>How It Works</h3>
<ol>
<li>
Feature collection 
– On each page load, Session Shredder tracks session activity: 
 – Session age (hours since first seen) 
 – Pageviews count 
 – Cart value (numeric) 
 – Whether anything was added to cart 
 – Geolocation hash (hashed billing/shipping country) 
 – Simple bounce indicator (single pageview, no cart) 
– Features are stored per-session in non-autoloaded options and never include raw session IDs or user identifiers.
</li>
<li>
Rule-based pruning 
– An hourly cron (<code>session_shredder_cron</code>) scans the WooCommerce session table for candidates based on age. 
– For each candidate, the plugin: 
 – Loads stored features 
 – Applies conservative rules like: 
 – Session older than a hard timeout window (e.g. 72 hours) 
 – Single pageview and no cart value 
– If the rules deem the session a low-value “zombie”, it is pruned.
</li>
<li>
Stats & visualization
– After each real run, Session Shredder records: 
 – Total pruned sessions (lifetime and today) 
 – A short history of recent runs, including how many sessions were pruned and how many remained active before/after each run 
– The admin dashboard renders a Chart.js line graph of active & pruned sessions per run via a secure AJAX endpoint, plus a compact “Recent runs” table.
</li>
</ol>
<h3>For developers</h3>
Session Shredder exposes a small set of hooks and CLI commands so you can integrate it into more advanced workflows without forking the plugin.
<h4>Hooks</h4>
– <code>session_shredder_features( array $features, string $session_hash )</code> 
 – Filter the behavior feature array before it is stored and later used for pruning decisions. 
 – <code>$session_hash</code> is a hashed identifier of the session (no raw IDs or PII).
– <code>session_shredder_base_age_hours( float $base_age_hours )</code> 
 – Adjust the base age window (in hours) before sessions are considered as prune candidates.
– <code>session_shredder_should_prune( bool $should_prune, array $features )</code> 
 – Override or refine the core rule-based decision for a given session.
– <code>session_shredder_feature_options_soft_limit( int $soft_limit )</code> 
 – Adjust the soft cap for how many per-session feature options (<code>session_shredder_features_*</code>) are kept in <code>wp_options</code> before garbage collection trims the oldest entries.
– <code>session_shredder_feature_options_gc_batch( int $batch_size )</code> 
 – Adjust how many feature options are removed per garbage-collection pass when the soft limit is exceeded. Larger values clean up faster; smaller values spread work over more runs.
– <code>session_shredder_before_run( float $base_age_hours, bool $dry_run )</code> 
 – Fires before a prune run (cron, manual, or CLI) starts.
– <code>session_shredder_after_run( int $pruned_count, bool $dry_run )</code> 
 – Fires after a prune run completes (dry-run or real).
– <code>session_shredder_pruned( int $pruned_count )</code> 
 – Fires after a real prune run that actually deletes sessions; useful for logging or additional cleanup.
<h4>WP-CLI commands</h4>
If WP-CLI is available, Session Shredder registers the following commands:
– <code>wp session-shredder analyze</code> 
 – Performs a dry run using the current rules and settings. 
 – Outputs the total number of sessions and how many would be pruned, without deleting anything.
– <code>wp session-shredder prune</code> 
 – Runs a real prune using the current rules and settings. 
 – Deletes matching sessions, updates stats, and logs a summary.

Session Shredder for WooCommerce

Smart rule-based pruning for WooCommerce 10.3+. Enhances experimental session storage with behavior signals to remove zombie sessions and cut DB size.

zeshanb

A simple shopping cart using shortcodes.
Be sure your permalinks in WordPress settings supports slug urls e.g. your-domain.tld/slug. Once you have proper permalink setting, Create a page with slug /cart. Then edit the cart page and add [easy_cart /] and [empty_cart /] shortcodes.
Create add to cart buttons using [add_to_cart /] shortcodes on other posts or pages of your WordPress site.
Use the following attributes to define your add_to_cart products:
<ol>
<li>itemid</li>
<li>product_name</li>
<li>product_desc</li>
<li>product_qty</li>
<li>price</li>
</ol>
Here is a example usage of add_to_cart shortcode using all the attributes. Be sure to use single quotes:
[add_to_cart itemid=’your-item-id’ product_name=’Your product name’ product_desc=’description of your product.’ product_qty=1 price=1.00 /]
You can have as many add_to_cart shortcodes as you like, in posts and pages.
Shopping cart allows you to store items and calculate total but doesn’t allow you to checkout. At least not yet as of version 1.2.
<iframe loading="lazy" class="youtube-player" width="750" height="422" src="https://www.youtube.com/embed/dN5QkERCRuo?version=3&rel=1&showsearch=0&showinfo=1&iv_load_policy=1&fs=1&hl=en-US&autohide=2&wmode=transparent" allowfullscreen="true" style="border:0;" sandbox="allow-scripts allow-same-origin allow-popups allow-presentation allow-popups-to-escape-sandbox"></iframe>

Easy Cart

A simple shopping cart plugin that adds cart and add-to-cart shortcodes to WordPress.

Session Shredder for WooCommerce vs Easy Cart