You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
During testing for #1, the importer did not list or import custom Tumblr blog pages. TBH, I don't know when/if this worked properly, but since it's a column listed on the importer, I would expect it to do so.
Steps to Reproduce
In Tumblr, click the Account icon, and under the blog section, select "Edit Appearance".
In the Custom Theme section, click the Edit theme button.
In the theme editor, scroll down and click "+ Add a page". Give the page a path, a name, and sample content, then click Save.
Click the arrow in the upper-left to return to the theme editor, and click Exit to leave the customizer.
In WordPress, navigate to Tools > Import, install the Tumblr importer if needed, and then run it. Follow the steps outlined in Add support for WordPress 6.1 #1 to create a Tumblr app, and to link your WordPress site to Tumblr.
Observe that the "Pages Imported" column lists "0", and running the importer does not update this value, nor import pages into WordPress.
Supplemental Assets
The text was updated successfully, but these errors were encountered:
@ironprogrammer Yeah, I noticed. It didn't work since the introduction of the new Tumblr API. Unfortunately there is no way to get the pages. I think that it's a good idea to remove that part. What do you think?
Yes, I agree that removing it would be clearer for users.
The Tumblr blog site functionality where pages live has a distinct "legacy" feel to it 😅. But to be certain, I've reached out to Tumblr to see if this endpoint is coming back, or if the feature should be removed for good.
During testing for #1, the importer did not list or import custom Tumblr blog pages. TBH, I don't know when/if this worked properly, but since it's a column listed on the importer, I would expect it to do so.
Steps to Reproduce
Supplemental Assets
The text was updated successfully, but these errors were encountered: