Shahi LegalFlowSuite

Troubleshooting Common Issues

Plugin Won’t Activate

Symptoms

    1. “Error activating plugin” message
    2. Plugin remains inactive
    3. No SLOS menu in admin
    4. Causes & Solutions

      Cause: PHP Version Too Old

    5. Requirement: PHP 7.4+
    6. Solution: Upgrade PHP version with hosting provider
    7. Check: SLOSSettingsSystem Info to verify
    8. Cause: WordPress Version Incompatible

    9. Requirement: WordPress 6.0+
    10. Solution: Upgrade WordPress to latest version
    11. Check: Dashboard → Updates
    12. Cause: Memory Limit Too Low

    13. Requirement: 256MB minimum (512MB recommended)
    14. Solution: Add to wp-config.php:
    15. `php
      define(‘WPMEMORYLIMIT’, ‘256M’);
      define(‘WPMAXMEMORY_LIMIT’, ‘512M’);
      `

      Cause: File Permissions

    16. Issue: Plugin can’t write to directories
    17. Solution: Fix permissions:
    18. `bash
      chmod -R 755 wp-content/plugins/shahi-legalflowsuite
      `

      Cause: Conflicting Plugin

    19. Issue: Another plugin prevents activation
    20. Solution:
    21. 1. Deactivate all other plugins
      2. Try activating SLOS
      3. Re-enable plugins one by one
      4. Identify conflicting plugin

      Debug Steps

    22. Enable WordPress debugging:
    23. `php
      // In wp-config.php
      define(‘WP_DEBUG’, true);
      define(‘WPDEBUGLOG’, true);
      define(‘WPDEBUGDISPLAY’, false);
      `

    24. Check error log:
    25. – Location: /wp-content/debug.log
      – Look for SLOS errors
      – Note exact error message

    26. Contact support with:
    27. – Error message
      – PHP version
      – WordPress version
      – Active plugins list

      Dashboard Won’t Load

      Symptoms

    28. Blank page when clicking SLOS menu
    29. “Nonce verification failed” message
    30. 500 Internal Server Error
    31. Solutions

      Clear WordPress Cache

    32. Via plugin (W3 Total Cache, WP Rocket, etc.)
    33. Or manually via FTP/SSH:
    34. `bash
      rm -rf wp-content/cache/
      `

      Check User Permissions

    35. Verify user has manage_options capability
    36. Ensure user is Administrator role
    37. Go to Users → Select user → Check “Administrator”
    38. Disable Plugins

    39. Deactivate all plugins except SLOS
    40. Try accessing dashboard
    41. Reactivate plugins one by one
    42. Identify culprit
    43. Increase PHP Resources

    44. In wp-config.php:
    45. `php
      define(‘WPMEMORYLIMIT’, ‘512M’);
      settimelimit(300);
      `

      Check Browser Console

    46. Open DevTools (F12)
    47. Go to Console tab
    48. Look for JavaScript errors
    49. Check Network tab for failed requests
    50. Database Tables Not Created

      Symptoms

    51. “Table doesn’t exist” errors
    52. Settings won’t save
    53. Blank dashboard metrics
    54. Solutions

      Reinstall Database

    55. Go to SLOSSettingsAdvanced
    56. Click Reinstall Database Tables
    57. Wait for completion
    58. Check if tables created
    59. Manual Check via phpMyAdmin

    60. Open phpMyAdmin
    61. Select your database
    62. Look for tables starting with slos_
    63. If empty, reinstall tables
    64. Check Database Permissions

    65. User must have CREATE TABLE permission
    66. User must have ALTER TABLE permission
    67. User must have INSERT, SELECT, UPDATE, DELETE permissions
    68. Check Disk Space

    69. Verify adequate disk space on server
    70. Database creation requires space
    71. Ask hosting provider if needed
    72. Review Error Log

    73. Check /wp-content/debug.log
    74. Look for database errors
    75. May show permission issues or MySQL version problems
    76. Consent Banner Not Showing

      Symptoms

    77. Banner doesn’t appear on frontend
    78. Users can interact without consenting
    79. Cookies set immediately
    80. Solutions

      Verify Module Enabled

    81. Go to SLOSSettingsModules
    82. Check “Consent Management” is enabled
    83. Click Save if changed
    84. Check Frontend Setting

    85. Go to Consent ManagementSettings
    86. Verify “Enable Banner on Frontend” is checked
    87. Verify “Auto-Load Banner” is checked
    88. Save settings
    89. Clear Cache Completely

    90. Browser cache
    91. WordPress cache plugin
    92. CloudFlare cache
    93. CDN cache
    94. Memcached/Redis cache
    95. Check JavaScript Errors

    96. Open page in browser
    97. Press F12 to open DevTools
    98. Go to Console tab
    99. Look for red error messages
    100. Check Network tab for failed assets
    101. Verify No CSS Conflicts

    102. Banner CSS might be hidden
    103. Try banner in incognito mode
    104. Test with all plugins disabled except SLOS
    105. Check Banner Position

    106. Is banner behind other elements?
    107. Check z-index conflicts
    108. Try different position (top vs bottom)
    109. Cookies Not Being Tracked

      Symptoms

    110. Consent records empty
    111. Cookie inventory shows zero cookies
    112. Analytics not recording
    113. Solutions

      Verify Scanner Enabled

    114. Go to Consent ManagementSettings
    115. Check “Enable Cookie Scanner” is enabled
    116. Click “Run Cookie Scan” manually
    117. Wait for completion
    118. Check for JavaScript Errors

    119. DevTools Console (F12)
    120. Look for errors in consent code
    121. Check Network tab for failed loads
    122. Browser Settings Blocking Cookies

    123. Test in private/incognito mode
    124. Check browser cookie settings
    125. Try different browser
    126. Test on different device
    127. Test Cookie Setting

    128. Accept consent in banner
    129. Check browser Storage:
    130. – DevTools → Application → Cookies
      – Look for cookie with site domain
      – Verify consent value stored

      Accessibility Scan Not Running

      Symptoms

    131. Scan button doesn’t work
    132. Progress popup doesn’t appear
    133. Scan seems to hang
    134. Solutions

      Check Module Enabled

    135. Go to SLOSSettingsModules
    136. Verify “Accessibility Scanner” is enabled
    137. Enable if disabled
    138. Increase PHP Timeout

    139. In wp-config.php:
    140. `php
      define(‘WPMEMORYLIMIT’, ‘512M’);
      settimelimit(600); // 10 minutes
      `

      Increase Server Timeout

    141. Edit .htaccess (if using Apache):
    142. `
      phpvalue maxexecution_time 600
      phpvalue memorylimit 512M
      `

      Check URL Accessibility

    143. Scan must reach your pages
    144. Test URL in browser
    145. If password protected, disable authentication for scan
    146. Verify no IP blocking
    147. Run Single Page Scan

    148. Instead of site-wide scan
    149. May help identify problematic pages
    150. Try scanning homepage first
    151. Check Error Log

    152. Location: /wp-content/debug.log
    153. Look for accessibility scanner errors
    154. May indicate resource issues
    155. DSR Requests Not Sending Emails

      Symptoms

    156. Users don’t receive verification emails
    157. Admin doesn’t get notifications
    158. Emails not appearing anywhere
    159. Solutions

      Verify SMTP Setup

    160. Go to SLOSSettingsEmail
    161. Click “Send Test Email”
    162. Check admin email for test message
    163. If doesn’t arrive, SMTP is misconfigured
    164. Check WordPress Mail Configuration

    165. Go to SLOSSystem Info
    166. Look for “Mail Setup” section
    167. Verify mail function not disabled
    168. Check mail server logs
    169. Whitelist SLOS Emails

    170. Some hosts filter plugin emails
    171. Add SLOS emails to whitelist
    172. Check spam/trash folder
    173. Ask hosting provider
    174. Test Mail Plugin

    175. Use “Test Mail” in Settings
    176. Check admin email address
    177. Verify it’s configured correctly
    178. Check spam filters
    179. Review Error Log

    180. Location: /wp-content/debug.log
    181. Look for mail() function errors
    182. May show SMTP connection issues
    183. Document Generation Failing

      Symptoms

    184. “Error generating document” message
    185. Export fails
    186. PDF won’t create
    187. Solutions

      Verify Company Profile Complete

    188. Go to Legal DocumentsCompany Profile
    189. Fill in all required fields
    190. Click Save
    191. Try generating document again
    192. Check File Permissions

    193. Documents need write permission
    194. Location: /wp-content/uploads/slos/
    195. Fix permissions:
    196. `bash
      chmod -R 755 wp-content/uploads/slos/
      `

      Increase PHP Memory

    197. Document generation memory intensive
    198. In wp-config.php:
    199. `php
      define(‘WPMEMORYLIMIT’, ‘512M’);
      `

      Check Disk Space

    200. Verify adequate space in uploads folder
    201. Ask hosting provider if full
    202. Clean up old documents if needed
    203. Try Different Format

    204. If PDF fails, try HTML export
    205. If HTML fails, try JSON export
    206. Helps identify specific issue
    207. Test with Simple Template

    208. Use “Standard” template
    209. Simpler templates need less resources
    210. Try more complex after success
    211. Modules Interfering with Each Other

      Symptoms

    212. Enabling one module breaks another
    213. Features stop working
    214. Unexpected behavior
    215. Solutions

      Check Execution Order

    216. Some modules depend on others
    217. Module Manager controls order
    218. Go to SLOSSettingsModule Order
    219. Re-order if needed
    220. Disable & Re-enable

    221. Disable problematic module
    222. Click Save
    223. Wait 30 seconds
    224. Re-enable module
    225. Click Save
    226. Clear All Caches

    227. WordPress cache
    228. Browser cache
    229. CDN cache
    230. Database cache (Redis/Memcached)
    231. Check for Conflicts

    232. Disable all modules
    233. Enable one module
    234. Test it works
    235. Enable next module
    236. Test
    237. Repeat to find conflict
    238. Reset Module Settings

    239. Go to module settings
    240. Click “Reset to Defaults”
    241. Reconfigure module
    242. Test functionality
    243. Performance Issues After Activation

      Symptoms

    244. Site slow after plugin activation
    245. Page load time increased
    246. Server CPU usage high
    247. Solutions

      Disable Modules Temporarily

    248. Keep only essential modules
    249. Enable others one by one
    250. Identify which causes slowdown
    251. Configure that module for performance
    252. Check Scanning Schedule

    253. Accessibility scans can be intensive
    254. Disable automatic scheduled scans
    255. Run manually during off-peak
    256. Go to SettingsScanning Schedule
    257. Optimize Database Queries

    258. Go to SettingsAdvanced
    259. Check “Query Optimization”
    260. Runs periodic optimization
    261. Helps with large data volumes
    262. Reduce Cookie Scan Frequency

    263. Scanner can impact performance
    264. Go to Consent ManagementSettings
    265. Change scan frequency from daily to weekly
    266. Run manually as needed
    267. Disable Debug Logging

    268. Debug logging adds overhead
    269. Go to SettingsAdvanced
    270. Uncheck “Debug Logging”
    271. Only enable when troubleshooting
    272. Check Hosting Resources

    273. Ask hosting provider about:
    274. – PHP memory available
      – CPU limits
      – Database performance
      – Disk I/O speed

      Getting Help

      Gather Information

      Before contacting support:

    275. Go to SLOSSystem Info
    276. Copy entire system information
    277. Note exact error messages
    278. Check /wp-content/debug.log
    279. List active plugins
    280. Note WordPress & PHP versions
    281. Contact Support

      Include:

    282. System info from above
    283. Error messages (exact text)
    284. Steps to reproduce issue
    285. What you’ve tried so far
    286. Hosting provider info
    287. Post in Forums

      WordPress.org plugin forums:

    288. Go to plugin page
    289. Click “Support” tab
    290. Search for similar issues first
    291. Provide all information above

Getting More Help

Next steps if issue persists:

  • Disable all plugins except SLOS
  • Switch to default WordPress theme
  • Try in fresh browser/private mode
  • Test on different device
  • Test on different network
  • Review detailed logs carefully
  • Contact hosting provider
  • Reach out to plugin developers
  • Share this article

    Was this article helpful?

    Help us improve our documentation

    Still need help?

    Our support team is ready to assist you with personalized guidance for your workspace.

    Submit a support ticket