PublishPress-Planner icon indicating copy to clipboard operation
PublishPress-Planner copied to clipboard

PublishPress conflicts with WordPress import

Open ckoerner opened this issue 4 years ago • 1 comments

We recently launched a community blog for the Wikimedia movement at diff.wikimedia.org. We're using PublishPress and I noticed a strange behavior when PublishPress is activated. When importing an XML export from another WordPress site, authorship is stripped from the imported blog posts. The blog posts also default to the current time and date instead of their original publish date. Deactivating PublishPress and running the importer is a workaround.

Expected Behavior

Setup a new WordPress site. Install PublishPress and activate. Import XML using /wp-admin/import.php Blog posts are imported with authorship intact.

Current Behavior

Setup a new WordPress site. Install PublishPress and activate. Import XML using /wp-admin/import.php Blog posts are imported with authorship blank and date sent to current date/time.

no-authorship

Possible Solution

I'm not sure what happens on import, if PublishPress has some hooks that touches authorship or date perhaps on import it id doing come check and breaks that? ¯\(ツ)

Note: I am using Co-authors Plus. Perhaps the conflict is there. I do not know. Deactivating that plugin made no change to the import process.

Steps to Reproduce (for bugs)

Setup a new WordPress site. Install PublishPress and activate. Import XML using /wp-admin/import.php

Specific to my experiences: We're running on WordPress VIP. When creating the site I setup a local instance in accordance to WordPress VIP's instructions: https://wpvip.com/documentation/vip-go/local-vip-go-development-environment/

I installed PublishPress and activated. I then went to import a valid backup from another site. I can't provide that backup, but we made 3 imports to diff.wikimedia.org, all with the same issue. I've used the theme unit test data to test sites in the past. https://wpcom-themes.svn.automattic.com/demo/theme-unit-test-data.xml

Context

I've worked around this issue as mentioned above, but if you all could take a look and confirm (or not!) this issue it might help other folks.

Your Environment

  • Version used: 2.2.0
  • Browser Name and version:
  • Operating System and version (desktop or mobile):
  • Link to your project: diff.wikimedia.org

ckoerner avatar Jul 15 '20 22:07 ckoerner

Hi @ckoerner thank you for the detailed report. This is a weird issue, but I will be checking it

andergmartins avatar Jul 27 '20 19:07 andergmartins