This guide helps you troubleshoot common problems encountered during ShahiLandin installation and activation.
Plugin Won’t Install
Symptom
You cannot install ShahiLandin through the WordPress admin interface or receive an error message during installation.
Possible Causes and Solutions
1. Insufficient File Permissions
Problem: WordPress cannot write to the /wp-content/plugins/ directory.
Solution:
- Connect to your server via FTP or cPanel File Manager
- Navigate to
/wp-content/plugins/ - Set folder permissions to
755or775 - Try installing the plugin again
- Check your current memory limit in ShahiLandin → System Info (if plugin is partially installed) or Tools → Site Health
- Increase PHP memory limit to at least 256MB by adding to
wp-config.php: - If that doesn’t work, contact your hosting provider to increase the limit
- Edit your
.htaccessfile (in WordPress root directory) - Add these lines:
- Extract the plugin ZIP file on your computer
- Connect via FTP/SFTP
- Upload the
ShahiLandinfolder to/wp-content/plugins/ - Go to Plugins in WordPress admin and activate ShahiLandin
- Delete the previously downloaded file
- Download ShahiLandin again from a reliable source
- Verify the file size matches the expected size
- Try installing again
- ShahiLandin requires WordPress 6.0 or higher
- Go to Dashboard → Updates
- Update WordPress to the latest version
- Important: Backup your site before updating
- Install ShahiLandin after updating WordPress
- ShahiLandin requires PHP 7.4 or higher (PHP 8.0+ recommended)
- Check your PHP version in Tools → Site Health → Info → Server
- Contact your hosting provider to upgrade to PHP 8.0 or higher
- Most hosts allow PHP version changes through cPanel or hosting dashboard
- ShahiLandin requires these PHP extensions:
- Contact your hosting provider to enable these extensions
- For cPanel servers, extensions can be enabled via Select PHP Version → Extensions
- Deactivate all other plugins
- Try activating ShahiLandin alone
- If it works, reactivate other plugins one by one to identify the conflict
- Common conflicting plugins:
- Once identified, keep the conflicting plugin deactivated or contact support
- Switch to a default WordPress theme (Twenty Twenty-Four)
- Try activating ShahiLandin
- If successful, the issue is with your theme
- Contact theme developer for compatibility
- Alternatively, use ShahiLandin’s Canvas Mode which bypasses theme templates
- ShahiLandin needs to create database tables during activation
- Your database user needs
CREATE,ALTER,INSERT,UPDATE,DELETE, andSELECTprivileges - Access phpMyAdmin or cPanel MySQL
- Check user privileges for your WordPress database
- Grant necessary permissions or contact hosting support
- Verify you’re logged in as a Super Admin
- Go to Network Admin → Plugins
- Click Network Activate (not regular Activate)
- If still failing, check
.htaccessandwp-config.phpfor multisite configuration errors - Ensure all subsites meet minimum requirements
- Deactivate the plugin
- Run the database cleanup:
- Reactivate ShahiLandin
- Check if tables were created by going to phpMyAdmin and looking for:
- If tables still missing, run manual migration:
- ShahiLandin needs write access to these directories:
- Set directory permissions to
755or775 - Set file permissions to
644or664 - Via SSH:
- Immediate fix: Deactivate via database
- Enable WordPress debugging in
wp-config.php: - Check
/wp-content/debug.logfor specific errors - Address the specific error found
- Try activating again
- Check user role and permissions
- Clear browser cache and cookies
- Try a different browser
- Check if menu was hidden:
- Deactivate and reactivate the plugin
- Check database write permissions
- Disable security plugins temporarily
- Check for JavaScript errors:
- Verify
wp_optionstable isn’t corrupted: - Verify post type was registered:
- If missing, deactivate and reactivate plugin
- Check user capabilities:
- Flush permalinks:
- Clear all caches (plugin, theme, server, CDN)
- ShahiLandin preserves settings in database even when deactivated
- Settings only delete on uninstall
- If lost, check:
- Landing pages remain in database as custom post type
- Check if they’re in trash:
- Check database:
- If found, they’re just hidden – flush permalinks
- If truly deleted, restore from backup
- Check System Status:
- Collect Error Information:
- Enable Debug Mode:
- Review Debug Log:
- Contact Support:
- ✅ Always backup before installing new plugins
- ✅ Keep WordPress, PHP, and plugins updated
- ✅ Use reputable hosting with adequate resources
- ✅ Test on staging site first (if available)
- ✅ Maintain adequate server resources (memory, disk space)
- ✅ Regular database optimization and cleanup
- ✅ Monitor error logs periodically
- Requirements and Compatibility
- Installation Guide
- Cache and Plugin Conflicts
For Linux/Unix servers (via SSH):
`bash
chmod 755 /path/to/wp-content/plugins/
`
2. PHP Memory Limit Too Low
Problem: The plugin file is large and exceeds your PHP memory limit.
Solution:
`php
define(‘WPMEMORYLIMIT’, ‘256M’);
`
3. Upload File Size Limit
Problem: The plugin ZIP file exceeds your server’s upload limit.
Solution Method 1 (Increase Upload Limit):
`apache
phpvalue uploadmax_filesize 64M
phpvalue postmax_size 64M
phpvalue maxexecution_time 300
phpvalue maxinput_time 300
`
Solution Method 2 (Manual Upload):
4. Corrupt ZIP File
Problem: The downloaded plugin file is corrupted or incomplete.
Solution:
5. WordPress Version Incompatibility
Problem: You’re running an outdated version of WordPress.
Solution:
Plugin Won’t Activate
Symptom
The plugin installs successfully but shows an error when you try to activate it.
Possible Causes and Solutions
1. PHP Version Too Old
Problem: Your server is running PHP 7.3 or older.
Error Message:
`
Parse error: syntax error, unexpected ‘?’, expecting variable (T_VARIABLE) in …/shahilandin.php
`
Solution:
2. Missing PHP Extensions
Problem: Required PHP extensions are not installed on your server.
Error Message:
`
Fatal error: Class ‘DOMDocument’ not found
`
Solution:
– dom (for HTML parsing)
– json (for data handling)
– mbstring (for character encoding)
– curl (for HTTP requests)
3. Plugin Conflict
Problem: Another plugin is conflicting with ShahiLandin.
Solution:
– Other landing page builders
– Security plugins with strict rules
– Caching plugins with aggressive optimization
4. Theme Conflict
Problem: Your active theme is incompatible with ShahiLandin.
Solution:
5. Insufficient Database Privileges
Problem: WordPress database user lacks necessary permissions.
Error Message:
`
Cannot create table ‘wpshahilandinanalytics’
`
Solution:
6. Multisite Installation Issues
Problem: Plugin won’t network activate on WordPress Multisite.
Solution:
Plugin Activates But Shows Errors
Symptom
ShahiLandin activates but displays warnings or errors in admin.
Possible Causes and Solutions
1. Database Tables Not Created
Problem: Activation completed but database tables are missing.
Solution:
– Install “WP Database Reset” plugin temporarily
– Reset only ShahiLandin tables (if they exist)
– wpshahilandinanalytics
– wpshahilandinexperiments
– Upload run-migrations.php from plugin folder to WordPress root
– Visit https://yoursite.com/run-migrations.php
– Delete the file after completion
2. File Permission Issues
Problem: Plugin cannot write to its directories.
Error Message:
`
Warning: fileputcontents(…): failed to open stream: Permission denied
`
Solution:
– /wp-content/plugins/ShahiLandin/assets/
– /wp-content/uploads/shahilandin/
`bash
chmod -R 755 wp-content/plugins/ShahiLandin/
mkdir -p wp-content/uploads/shahilandin
chmod 755 wp-content/uploads/shahilandin
`
3. White Screen of Death (WSOD)
Problem: WordPress admin shows blank white screen after activation.
Solution:
– Access phpMyAdmin
– Go to wp_options table
– Find row where optionname = activeplugins
– Edit option_value and remove ShahiLandin reference
– Save changes
`php
define(‘WP_DEBUG’, true);
define(‘WPDEBUGLOG’, true);
define(‘WPDEBUGDISPLAY’, false);
`
Post-Activation Issues
No Menu Item Appears
Problem: ShahiLandin activated successfully but no menu appears in admin.
Solution:
– You need at least Editor role
– Super Admin for multisite
– Go to Screen Options (top right)
– Ensure ShahiLandin items are checked
Settings Not Saving
Problem: Changes to plugin settings don’t persist.
Solution:
– Open browser Console (F12)
– Look for red error messages
– Take screenshot and contact support
– Run database repair: Add to wp-config.php:
`php
define(‘WPALLOWREPAIR’, true);
`
– Visit: https://yoursite.com/wp-admin/maint/repair.php
– Remove the define line after repair
Can’t Create Landing Pages
Problem: “Add New Landing Page” button doesn’t work or shows errors.
Solution:
– Go to Tools → Site Health → Info
– Check if shahi_landing appears under Post Types
– User needs createshahilandings capability
– Administrator and Editor roles have this by default
– Go to Settings → Permalinks
– Click Save Changes without changing anything
Reactivation After Deactivation
Lost Settings After Reactivation
Problem: Plugin settings reset to defaults when reactivated.
Solution:
1. Database for shahilandin% options in wpoptions table
2. Backup/restore functionality
3. WordPress revisions (for page content)
Lost Landing Pages
Problem: Landing pages disappeared after reactivation.
Solution:
– Go to Landing Pages → Trash
– In phpMyAdmin, run:
`sql
SELECT * FROM wpposts WHERE posttype = ‘shahi_landing’;
`
Getting Additional Help
If these solutions don’t resolve your issue:
– Go to ShahiLandin → System Info
– Review all system requirements
– Note any warnings in red
– Error message (exact text)
– PHP version
– WordPress version
– Active theme
– Active plugins list
– Hosting provider
`php
// In wp-config.php
define(‘WP_DEBUG’, true);
define(‘WPDEBUGLOG’, true);
define(‘WPDEBUGDISPLAY’, false);
`
– Check /wp-content/debug.log
– Look for ShahiLandin-related errors
– Include all information collected above
– Attach debug log (if available)
– Provide steps to reproduce the issue
Prevention Tips
To avoid installation and activation issues:
—
Related Articles:
Share this article
Still need help?
Our support team is ready to assist you with personalized guidance for your workspace.