In attempting to publish an article to child sites, MainWP showed an error message. The “New Post” success form typically shows that all posts were successful. This morning, it showed: “ERROR: Empty post id.” In checking the child website (both frontend and admin), the post is not there!
The post was to just one site. However, the “success” message indicates it was published to 3 sites!
Help!
Hey @richfarr
Was this a one-time occurrence, or did you get the same error when trying to publish a post on that site multiple times?
Have you tried creating a post on any other child site via MainWP Dashboard?
And can you please post the community system report from your MainWP Dashboard for review? The report is located in your Dashboard under Info → Server, on the top right of the page.
Be sure to use the button like the one below; this button hides all your private information:
Pressing the button auto-copies the report to your clipboard then just paste it in a reply here.
Hi Bojan,
I tried publishing the a couple of times. We have websites grouped by tags - so I tried publishing to the individual site and again to the “tag” group. Each time I got the error message.
I just tried to post to the other sites and it appears one was successful, two got the error message.
System Report below:
### WordPress Check Required Detected Status ###
FileSystem Method = direct direct Pass
MultiSite Disabled =true true Pass
WordPress Memory Limit >=64M 256M Pass
WordPress Version >=3.6 6.1.1 Pass
### PHP Required Detected Status ###
cURL Extension Enabled =true true Pass
cURL SSL Version >=OpenSSL/1.1.0 OpenSSL/1.1.1q-fips Pass
cURL Timeout >=300 seconds 40 Warning
cURL Version >=7.18.1 7.66.0 Pass
PCRE Backtracking Limit >=10000 1000000 Pass
PHP Allow URL fopen N/A YES
PHP Disabled Functions N/A No functions disabled.
PHP Exif Support N/A YES ( V7.4.)
PHP IPTC Support N/A YES
PHP Loaded Extensions N/A Core, PDO, Phar, Reflection, SPL, SimpleXML, Zend OPcache, apache2handler, bcmath, bz2, calendar, ctype, curl, date, dba, dom, enchant, exif, fileinfo, filter, ftp, gd, gettext, gmp, hash, iconv, imap, intl, json, libxml, mbstring, memcached, mysqli, mysqlnd, openssl, pcre, pdo_mysql, pdo_pgsql, pdo_sqlite, pgsql, posix, pspell, session, shmop, soap, sockets, sodium, sqlite3, standard, sysvmsg, sysvsem, tidy, tokenizer, xml, xmlreader, xmlrpc, xmlwriter, xsl, zip, zlib
PHP Max Execution Time >=30 seconds 120 Pass
PHP Max Input Time >=30 seconds 120 Pass
PHP Memory Limit >=128M 768M Pass
PHP Post Max Size >=2M 256M Pass
PHP Safe Mode Disabled =true true Pass
PHP Upload Max Filesize >=2M 256M Pass
PHP Version >=7.0 7.4.33 Pass
PHP XML Support N/A YES
SSL Extension Enabled =true true Pass
SSL Warnings = empty Pass
### MySQL Required Detected Status ###
MySQL Client Encoding N/A utf8
MySQL Mode N/A NO_ENGINE_SUBSTITUTION
MySQL Version >=5.0 5.7.39-42-log Pass
### Server Configuration Detected Value ###
Accept Content text/html,application/xhtml+xml,application/xml;q=0.9,image/avif,image/webp,image/apng,*/*;q=0.8,application/signed-exchange;v=b3;q=0.9
Accept-Charset Content N/A
Architecture 64 bit
Gateway Interface CGI/1.1
HTTPS ON
Memory Usage 66.66 MB
Operating System Linux
Request Time 1671119530
Server Protocol HTTP/1.0
Server self connect Response Test O.K.
Server Software Apache
User Agent Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/108.0.0.0 Safari/537.36
### MainWP Dashboard Settings Detected Value ###
Abandoned plugins/themes tolerance
Basic uptime monitoring enabled Yes
Cache control enabled No
MainWP Dashboard Version Latest: 4.3.1 | Detected: 4.3.1 Pass
MainWP legacy backups enabled No
Maximum number of pages to return
Maximum number of posts to return 50
Maximum simultaneous install and update requests
Maximum simultaneous requests 4
Maximum simultaneous requests per ip1
Maximum simultaneous sync requests
Minimum delay between requests 200
Minimum delay between requests to the same ip1000
Number of child sites 4
Optimize for shared hosting or big networksNo
Plugin advanced automatic updates enabledNo
Primary backup system MainWP Legacy Backups
REST API enabled No
Site health monitoring enabled Yes
Theme advanced automatic updates enabledNo
Use WP Cron No
WP Core advanced automatic updates enabledYes
### Extensions Version License Status ###
MainWP Custom Dashboard Extension 4.0.2 Actived Pass
MainWP Post Dripper Extension 4.0.3 Actived Pass
MainWP WordPress SEO Extension 4.0.1 Actived Pass
### Plugin Version Status ###
Accessibility by UserWay 2.5.0 Inactive
AddToAny Share Buttons 1.8.5 Inactive
Advanced Editor Tools (previously TinyMCE Advanced)5.6.0 Active
Akismet Anti-Spam 5.0.2 Inactive
Beaver Builder Plugin (Pro Version)2.4.2.4 Inactive
Beaver Themer 1.2.3.4 Inactive
Branda Pro 3.4.8 Inactive
Classic Editor 1.6.2 Active
Custom Sidebars 3.36 Inactive
Defender Pro 3.7.0 Active
Enable Media Replace 4.0.1 Inactive
Google Analytics for WordPress by MonsterInsights8.11.0 Inactive
Inactive Logout 3.0.11 Inactive
LightStart - Maintenance Mode, Coming Soon and Landing Page Builder2.6.1 Inactive
MainWP Dashboard 4.3.1 Active
Ninja Beaver Lite Addons for Beaver Builder2.4.5 Inactive
Ninja Forms 3.6.14 Inactive
PowerPack for Beaver Builder 2.17.1 Inactive
reCaptcha by BestWebSoft 1.70 Active
Redirection 5.3.6 Inactive
SiteGround Optimizer 7.2.9 Active
Smush Pro 3.12.3 Active
WordPress Backup & Security Plugin - BlogVault4.84 Active
WP Sticky Sidebar 1.3.8 Inactive
WPMU DEV Dashboard 4.11.17 Active
Yoast Duplicate Post 4.5 Active
Yoast SEO 19.12 Active
Hey Bojan,
Upon further investigation, we have discovered the child sites had an old version of the plugin (4.2.6). Upon upgrading to the latest version (4.3.1) and attempting to publish the posts again - it worked!
So we are back in business!
1 Like
Perfect, I’m glad you managed to isolate and solve the issue.
Bojan,
A follow-up question about this issue. Do you think this was an isolated incident, or do we need to check the individual child plugins on websites before we publish new content every time? Are updates not backward compatible with previous versions of the plugin?
1 Like
Old versions of MainWP Child plugin are backward compatible for the most part, but changes made to the Dashboard plugin may sometime mandate a change to the Child plugin. And in this case, the Child v4.2.6 was already 4 months old.
Which is why we strongly recommend to keep MainWP Child plugin always up to date, and in lock-step with MainWP Dashboard.
Easiest way to do so is to enable automatic updates for MainWP Child in the MainWP Dashboard by following this help article: Plugins Auto Updates - MainWP Documentation
This topic was automatically closed 24 hours after the last reply. New replies are no longer allowed.