Skip to main content
< All Topics
Print

Farmers Bounty – Troubleshooting Guide

Farmers Bounty – Troubleshooting Guide

Solutions to common issues and problems with the Farmers Bounty plugin.

Table of Contents

  1. Installation Issues
  2. Activation Problems
  3. Settings Not Saving
  4. Display Issues
  5. Performance Problems
  6. Conflict Resolution
  7. Error Messages
  8. Getting Additional Help

   // Add to wp-config.php
   @ini_set('upload_max_size', '64M');
   @ini_set('post_max_size', '64M');

## Installation Issues

### Cannot Upload Plugin

Symptoms: Error when trying to upload plugin ZIP file

Solutions:

1. Check file size limits

2. Manual installation

– Extract ZIP file on your computer

– Upload via FTP to /wp-content/plugins/

– Activate through WordPress admin

3. Contact hosting provider

– They may need to increase upload limits

### Plugin Files Not Found

Symptoms: “Plugin file does not exist” error

Solutions:

1. Verify folder name is farmers-bounty-plugin

2. Check that farmers-bounty.php exists in the plugin folder

3. Re-upload the plugin

4. Check file permissions (should be 644 for files, 755 for directories)

Activation Problems

White Screen After Activation

Symptoms: Blank white screen when activating

Solutions:

  1. Access via FTP
  • Navigate to /wp-content/plugins/
  • Rename farmers-bounty-plugin folder
  • WordPress will deactivate it automatically
  1. Enable debugging

   // Add to wp-config.php
   define('WP_DEBUG', true);
   define('WP_DEBUG_LOG', true);
   define('WP_DEBUG_DISPLAY', false);
  • Check /wp-content/debug.log for errors
  1. Check PHP version
  • Minimum required: PHP 7.2
  • Check current version: php -v

“Cannot Redeclare Class” Error

Symptoms: Fatal error about class already declared

Solutions:

  1. Check for duplicate plugin installations
  2. Deactivate conflicting plugins
  3. Clear opcache:

   opcache_reset();

Plugin Not Appearing in Menu

Symptoms: No Farmers Bounty menu item after activation

Solutions:

  1. Verify you’re logged in as Administrator
  2. Check user capabilities
  3. Clear browser cache
  4. Try different browser
  5. Deactivate and reactivate the plugin

Settings Not Saving

Changes Don’t Persist

Symptoms: Settings revert after saving

Solutions:

  1. Check file permissions

   chmod 755 /path/to/wp-content
   chmod 644 /path/to/wp-content/plugins/farmers-bounty-plugin/*
  1. Database issues
  • Verify database user has write permissions
  • Check database connection in wp-config.php
  1. Plugin conflicts
  • Deactivate caching plugins temporarily
  • Deactivate security plugins temporarily
  • Test with default theme
  1. Browser issues
  • Clear browser cache
  • Disable browser extensions
  • Try incognito/private mode

“Nonce Verification Failed”

Symptoms: Error message when saving settings

Solutions:

  1. Clear browser cookies
  2. Log out and log back in
  3. Check for clock synchronization issues
  4. Increase nonce lifetime:

   add_filter('nonce_life', function() {
       return 4 * HOUR_IN_SECONDS;
   });

Display Issues

Styles Not Loading

Symptoms: Plugin pages look unstyled

Solutions:

  1. Clear cache
  • Browser cache
  • WordPress cache plugins
  • Server-side cache
  1. Check asset loading
  • View page source
  • Look for farmers-bounty CSS files
  • Check browser console for 404 errors
  1. File permissions

   chmod 644 /path/to/farmers-bounty-plugin/assets/css/*
  1. Disable minification
  • Temporarily disable optimization plugins
  • Regenerate minified files

JavaScript Not Working

Symptoms: Interactive features don’t work

Solutions:

  1. Check browser console
  • Press F12
  • Look for JavaScript errors
  • Note specific error messages
  1. jQuery conflicts
  • Ensure jQuery is loaded
  • Check for noConflict issues
  1. Script loading order
  • Verify admin.js is loading
  • Check dependencies are loaded first

Performance Problems

Slow Admin Dashboard

Symptoms: Admin pages load slowly

Solutions:

  1. Disable unnecessary plugins
  • Deactivate unused plugins
  • Remove old, inactive plugins
  1. Optimize database

   OPTIMIZE TABLE wp_options;
  1. Enable caching
  • Use object caching
  • Enable page caching
  • Use CDN for assets
  1. Increase PHP limits

   memory_limit = 256M
   max_execution_time = 300

High Memory Usage

Symptoms: Memory exhausted errors

Solutions:

  1. Increase PHP memory limit in wp-config.php:

   define('WP_MEMORY_LIMIT', '256M');
   define('WP_MAX_MEMORY_LIMIT', '512M');
  1. Check for memory leaks in custom code
  2. Optimize queries and data processing

Conflict Resolution

Plugin Conflicts

Symptoms: Issues when other plugins are active

Solutions:

  1. Identify conflicting plugin
  • Deactivate all other plugins
  • Activate one by one
  • Test after each activation
  1. Common conflicts
  • Caching plugins: Clear cache, regenerate
  • Security plugins: Whitelist Farmers Bounty
  • SEO plugins: Usually no conflicts
  1. Report conflicts
  • Document conflicting plugin name/version
  • Contact support for both plugins

Theme Conflicts

Symptoms: Display issues or functionality problems

Solutions:

  1. Test with default theme
  • Switch to Twenty Twenty-Three
  • If problem resolves, it’s theme-related
  1. Check theme functions
  • Review theme’s functions.php
  • Look for conflicting hooks
  1. Template overrides
  • Ensure theme isn’t overriding plugin templates incorrectly

Error Messages

“Headers Already Sent”

Cause: Output before HTTP headers

Solutions:

  1. Remove whitespace before in plugin files
  2. Check for echo/print statements in activation hooks
  3. Verify file encoding is UTF-8 without BOM

"Database Error"

Cause: Database query failed

Solutions:

  1. Check database credentials in wp-config.php
  2. Verify database server is running
  3. Check user permissions on database
  4. Review database error logs

"Permission Denied"

Cause: File system permissions issue

Solutions:


# Set correct permissions
find /path/to/farmers-bounty-plugin -type f -exec chmod 644 {} \;
find /path/to/farmers-bounty-plugin -type d -exec chmod 755 {} \;

"Class Not Found"

Cause: Autoloading issue

Solutions:

  1. Verify all class files are present
  2. Check include paths in main plugin file
  3. Clear opcache
  4. Reinstall plugin

Getting Additional Help

Before Contacting Support

Gather this information:

  1. System Information
  • WordPress version
  • PHP version
  • MySQL version
  • Server software (Apache/Nginx)
  • Hosting provider
  1. Plugin Information
  • Farmers Bounty version
  • Active plugins (name and version)
  • Active theme
  1. Error Details
  • Exact error message
  • Steps to reproduce
  • Screenshots
  • Browser console errors
  • Server error logs

Enable Debug Mode


// Add to wp-config.php
define('WP_DEBUG', true);
define('WP_DEBUG_LOG', true);
define('WP_DEBUG_DISPLAY', false);
define('SCRIPT_DEBUG', true);

Check /wp-content/debug.log for error details.

Contact Support

When contacting support, include:

  • All information from "Before Contacting Support"
  • What you've already tried
  • When the problem started
  • Any recent changes to your site

Quick Reference

Common Solutions Checklist

  • [ ] Clear all caches (browser, plugin, server)
  • [ ] Deactivate other plugins temporarily
  • [ ] Switch to default theme temporarily
  • [ ] Check file permissions
  • [ ] Enable debug mode
  • [ ] Review error logs
  • [ ] Update WordPress, PHP, and plugins
  • [ ] Check database connection
  • [ ] Verify user permissions
  • [ ] Try different browser

File Permissions


Directories: 755
Files: 644
wp-config.php: 600 (recommended)

Useful Commands


# Check PHP version
php -v

# Check file permissions
ls -la /path/to/plugin

# Set permissions
chmod -R 755 /path/to/plugin
chmod -R 644 /path/to/plugin/*.php

# Check Apache error log
tail -f /var/log/apache2/error.log


Botanical Garden Skills

If you are using the Botanical Garden AI Skills (30 skills across horticulture, science, education, and outreach) and experiencing issues:

  1. Skills not appearing in Cursor/Codex — Verify the SKILL.md files exist in ~/.cursor/skills/botanical-/SKILL.md and ~/.codex/skills/botanical-/SKILL.md
  2. Skills not triggering — Skills activate based on their description field. Use the skill name directly (e.g., "Use the botanical-ipm-specialist skill") to invoke explicitly
  3. Re-syncing skills — Run the sync script from CANONICAL-SOURCE.md in operations/Skills/Claude-Skills/ to re-deploy from canonical source to Cursor and Codex

Still having issues? Contact plugin support with the information gathered from this guide.

Version: 1.0.0
Last Updated: March 19, 2026

Table of Contents