Changes between Version 1 and Version 2 of Ticket #42814, comment 8
- Timestamp:
- 12/17/2017 12:06:50 AM (7 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #42814, comment 8
v1 v2 1 I ran into this issue (on one site) while I was performing upgrade/failover automation tests against multiple WP sites at the same time.1 I ran into this issue while performing upgrade/failover tests against multiple WP sites at the same time - but encountered this error on only one site. 2 2 3 The site exhibiting this issue is very simple and using a 3-year old premium theme by StudioPress called Executive Pro which uses Genesis (also by StudioPress) as its parent theme. 4 - I can share additional information/data from the site in question if necessary (please contact me offline as I can't post it publicly). 3 The "problem site" is very simple and is using a 3-year old premium theme by StudioPress called Executive Pro which uses Genesis (also by StudioPress) as its parent theme. 5 4 - Because the same actions were performed against multiple sites, and only one exhibited this error, it appears to be caused by something site specific (not mere actions alone). 6 5 … … 21 20 - I temporarily stopped the error by commenting out lines 284-285 as they don't appear to apply to the "problematic site". (I did not need to change, or comment out, and other lines) 22 21 23 Please let me know if there's anything further I can share to help.22 I can share additional information/data from the site in question if necessary (please contact me offline as I can't post it publicly).