Hi Calin,
Thank you for the detailed reply. I understand the workaround you are suggesting, however I’d like to clarify why this does not fully address the core issue.
Using ACF instead of Newspaper’s native post fields is technically possible, but in practice this means abandoning the theme’s built-in content system rather than solving the problem with it.
The main concerns with this approach are:
• The Newspaper theme already provides native fields such as Subtitle and Source, which are tightly integrated into post templates and modules.
• Suggesting to replace them with ACF fields means duplicating functionality that already exists in the theme.
• For long-term projects, this creates extra technical debt and dependency on custom solutions instead of using the theme as intended.
More importantly, this does not solve the original problem: mass editing and updating theme-specific fields for already published posts.
My expectation is not necessarily that Newspaper fields must use WP All Import specifically, but that:
• theme custom fields can be treated as standard post meta,
• they can be accessed programmatically,
• and they can be updated in bulk via modern content workflows.
So I’d like to ask more directly, from an architectural standpoint:
• Are Newspaper’s native post fields (Subtitle, Source, etc.) designed to be mass-editable for existing posts, or not?
• Are these fields intentionally isolated from standard post meta and third-party tools?
• Is this a conscious design decision, or a technical limitation of the current implementation?
If the official recommendation is to avoid using Newspaper’s native post fields for scalable projects and instead rely on ACF or custom modules, it would be very helpful to state this clearly in the documentation.
I’m trying to evaluate Newspaper for long-term, content-heavy projects, and this point is critical for that decision.
Thank you for your honesty and clarification.
Best regards,
Aleksey
Hi Calin,
Thank you for the clarification.
I’d like to add an important detail about my use case, because the main problem is not only importing articles into a new site.
In many real scenarios, I already have:
- an existing website,
- hundreds or thousands of published posts,
- content migrated from another theme or setup.
After switching to Newspaper, theme-specific fields such as Subtitle, Source, etc. are empty — and I need a way to
mass update or fill these fields for already published posts.
This is where standard WordPress Import/Export or full site migration tools do not fully solve the problem:
- full migration copies everything “as is”, but does not help when data needs to be changed or enriched,
- WordPress Tools → Export/Import does not allow structured mapping or bulk editing of specific fields,
- modern workflows rely heavily on bulk operations (CSV/XML-based import/export), not manual editing.
From a practical standpoint, it feels quite strange in 2025 that theme custom fields cannot be reliably detected and mass-edited via import/export tools.
Ten years ago, editing fields manually was acceptable. Today, many projects depend on scalable content operations, migrations, and automation.
That’s why I’d like to ask more directly:
- Does Newspaper officially support bulk editing / bulk updating of its custom post fields for existing posts?
- Are there plans to make these fields fully compatible with third-party import/export tools by exposing them as standard post meta?
- If this is not currently supported, is this something that could be addressed in future updates?
I really like the Newspaper theme and have used it for many projects, but between the limitations of the page editor and now this issue with custom fields,
it does raise concerns about long-term scalability compared to other modern themes.
I’m asking this not as a complaint, but to understand whether this limitation is:
- a known issue,
- a design decision,
- or something that may be improved soon.
Thanks again for your time and transparency.
Best regards,
Aleksey
