__group__ ticket summary owner component priority severity milestone type _status workflow created modified _description _reporter Import 23276 WordPress Importer: Update existing navs instead of new Import normal normal WordPress.org defect (bug) new has-patch 2013-01-23T17:00:06Z 2020-10-01T19:25:32Z "A possible solution (reuses logic present in the code): {{{ $menu_item_db_id = (int) $item['post_id']; $original_object = get_post( $menu_item_db_id ); if ( is_null( $original_object ) ) { $post_parent = (int) $item['post_parent']; if ( $post_parent ) { // if we already know the parent, map it to the new local ID if ( isset( $this->processed_posts[$post_parent] ) ) { $post_parent = $this->processed_posts[$post_parent]; // otherwise record the parent for later } else { $this->post_orphans[intval($post['post_id'])] = $post_parent; $post_parent = 0; } } // map the post author $author = sanitize_user( $item['post_author'], true ); if ( isset( $this->author_mapping[$author] ) ) $author = $this->author_mapping[$author]; else $author = (int) get_current_user_id(); $postdata = array( 'import_id' => $item['post_id'], 'post_author' => $author, 'post_date' => $item['post_date'], 'post_date_gmt' => $item['post_date_gmt'], 'post_content' => $item['post_content'], 'post_excerpt' => $item['post_excerpt'], 'post_title' => $item['post_title'], 'post_status' => $item['status'], 'post_name' => $item['post_name'], 'comment_status' => $item['comment_status'], 'ping_status' => $item['ping_status'], 'guid' => $item['guid'], 'post_parent' => $post_parent, 'menu_order' => $item['menu_order'], 'post_type' => $item['post_type'], 'post_password' => $item['post_password'] ); $menu_item_db_id = wp_insert_post( $postdata, true ); if ( is_wp_error( $menu_item_db_id ) ) { $post_type_object = get_post_type_object( $item['post_type'] ); printf( __( 'Failed to import %s “%s”', 'wordpress-importer' ), $post_type_object->labels->singular_name, esc_html($item['post_title']) ); if ( defined('IMPORT_DEBUG') && IMPORT_DEBUG ) echo ': ' . $post_id->get_error_message(); echo '
'; } } $id = wp_update_nav_menu_item( $menu_id, $menu_item_db_id, $args ); }}}" WraithKenny Import 52740 WordPress Importer: Add vertical space between inputs Import normal normal WordPress.org defect (bug) new has-patch 2021-03-09T20:47:55Z 2021-04-08T20:17:12Z Need bottom space between 2 inputs ravipatel Import 6269 RSS Import Doesn't Properly Strip CDATA Tags Import normal normal WordPress.org defect (bug) new dev-feedback 2008-03-18T00:58:13Z 2019-03-15T00:40:20Z "When importing an RSS feed that uses the tag as opposed to , I noticed that WP's RSS import doesn't strip the CDATA tags as it does for the . =========Code Lines (83-87)=============== {{{ if (!$post_content) { // This is for feeds that put content in description preg_match('|(.*?)|is', $post, $post_content); $post_content = $wpdb->escape($this->unhtmlentities(trim($post_content[1]))); } }}} ===================================== I tweaked the code to solve the problem (see below) ==========Tweaked Code=============== {{{ if (!$post_content) { // This is for feeds that put content in description preg_match('|(.*?)|is', $post, $post_content); $post_content = str_replace(array (''), '',$wpdb->escape($this->unhtmlentities(trim($post_content[1])))); } }}} ====================================== I'd be happy to submit a patch, except I'm not quite that savvy yet. It would be great it someone could incorporate it. Thanks." sweetdeal Import 5678 Respectfully strip newlines in some importers hansengel* Import normal normal WordPress.org enhancement accepted 2008-01-16T11:20:02Z 2019-03-15T00:39:32Z "Filing this as an enhancement because it could do with some discussion and insight from wiser and more experienced heads before being labelled ""defect"". :-) I noticed while helping some users import their blogs that importers of HTML content (such as the RSS importer) don't tidy up superfluous newlines in the import format, which results in unnecessary {{{
}}} elements after {{{wpautop()}}} filtering for display. They turn up in the editor too, which reinforces the problem. I've adapted one of the filter functions to strip superfluous newlines, and changed my RSS importer to use it. The results have been warmly welcomed by users, who no longer have to clean up their imported blog content. ;-) {{{strip_newlines()}}} should probably go into {{{wp-includes/formatting.php}}}, if there isn't already a function that already serves this purpose. I couldn't find one, so I adapted this. Given that similar HTML block/inline-savvy string-replacement code exists in other formatting functions, perhaps there's an opportunity for some refactoring here? I feel kind of silly proposing a function that is almost entirely duplicated from other code in the core. I've used it immediately before the ""Clean up content"" section in {{{wp-admin/import/rss.php}}}'s {{{get_posts()}}}, and in an Advogato importer that I've written (which also uses HTML as the content format). {{{ function strip_newlines($text) { // Respectfully strip unnecessary newlines $textarr = preg_split(""/(<[^>]+>)/Us"", $text, -1, PREG_SPLIT_DELIM_CAPTURE); $stop = count($textarr); $skip = false; $output = ''; // loop stuff for ($ci = 0; $ci < $stop; $ci++) { $curl = $textarr[$ci]; if (! $skip && isset($curl{0}) && '<' != $curl{0}) { // If it's not a tag $curl = preg_replace('/[\n\r]+/', ' ', $curl); } elseif (strpos($curl, ' and expressions" westi Import normal normal WordPress.org defect (bug) assigned dev-feedback 2010-12-10T04:45:17Z 2017-05-23T15:16:47Z "There is a note on plugins.trac ticket 1231 that says this should be handled in core.trac instead, so I'm cross-posting it here. The patch and ticket were originally added by a-bishop: http://plugins.trac.wordpress.org/ticket/1231 Reproduction steps: 1. Create a LiveJournal? entry that has in it. Note that this is XML-ish 2. Try to use the livejournal-importer on this post. Bug The gets ignored because the regular expression is too strict. I've attached a patch that makes LiveJournal? Importer recognize the XML-ish version. Patch:[[BR]] http://plugins.trac.wordpress.org/attachment/ticket/1231/livejournal-importer.patch" designsimply Import 26247 Importer fails when importing from a server on a private network Import normal normal WordPress.org defect (bug) new 2013-11-25T22:18:00Z 2018-03-02T17:08:23Z "WordPress import (using the wordpress-importer plugin) does not work correctly if both machines are on the same private network. Text content imports, but all media imports fail. I have traced the problem down to a test that is done in wp-includes/http.php. Though i am not deeply familiar with the WordPress code base, the test seems unnecessary to me, and if it is commented out then the import function will behave as expected. I have included a patch against WordPress 3.6.1 that demonstrates where the problematic test is and resolves the issue." dramaley Import 24995 Importer does not check to see if DOM is available Import normal normal WordPress.org defect (bug) new 2013-08-08T20:55:34Z 2017-02-21T09:11:58Z "I have a WordPress network with many blogs. I exported a few posts from one blog (export file attached with some details sanitized). I then imported the posts into another blog. Not only does the import probably do nothing, the '''/''blogname''/wp-admin/import.php''' page stops rendering after: {{{

Import WordPress

}}} That is, if you do a view source on the page, the above '''h2''' element is the last thing you see. Expected behavior: execution does not stop mid-page, and if there is an error, it is displayed for logged-in administrative users. I am logged in as a network administrator." novasource Import 39301 Importer associates all posts with uncategorized term in WP4.7 PHP7 Import normal normal WordPress.org defect (bug) new 2016-12-16T01:00:20Z 2017-04-01T08:33:47Z "The WordPress Importer plugin fails to remove the uncategorized term from the post which has at least one category set. It's a pretty quick fix, though. wordpress-importer.php after line 729 Insert: {{{#!php if ( 'category' == $term['domain'] ) $post_is_categorized = TRUE; }}} wordpress-importer.php after line 753 Insert: {{{#!php if ( isset( $post_is_categorized ) && $post_is_categorized ) { wp_remove_object_terms( $post_id, 'uncategorized', 'category' ); unset( $post_is_categorized ); } }}} And BTW, is there somewhere I can make pull requests for WP like on github? That will make it much easier to suggest code changes. " staymanhou General 60600 found some spelling mistakes swissspidy General normal normal WordPress.org defect (bug) reviewing 2024-02-22T11:47:53Z 2024-02-22T12:10:41Z "I found some spelling mistakes in the WordPress Plugin documentation No.1 ---- https://developer.wordpress.org/plugins/shortcodes/shortcodes-with-parameters/#parsing-attributes:~:text=shortcode.%20In%20the-,exampe,-above%2C%20it%20will It will be - ""example"" not exampe. No.2 ---- https://developer.wordpress.org/plugins/internationalization/how-to-internationalize-your-plugin/#basic-strings:~:text=To%20echo%20a,instead%20of%20writing%3A and it will be ""translation"" not tranlsation. " azimjamshed Import 56858 Blogger Importer: Undefined (dynamic) properties Import normal normal WordPress.org defect (bug) new 2022-10-19T21:24:34Z 2022-10-21T01:29:57Z "Under PHP 7.4, the Blogger Importer plugin causes notices like the following: ''If new posts are imported:'' Undefined property: Blogger_Importer::$posts_done in ../blogger-importer/blogger-importer.php on line 408 == Background [https://github.com/WordPress/blogger-importer/commit/f1c9d6a7fe42fe4b88b475c9a92a96bd7cee8dba f1c9d6a7] introduced several dynamic properties to the `Blogger_Importer` class, such as counters for skipped and imported posts. In PHP 8.0 dynamic properties log as warnings, [https://php.watch/versions/8.2/dynamic-properties-deprecated in 8.2 as deprecations], and in 9.0 result in fatal errors. " ironprogrammer Import 56857 Blogger Importer: File class-wp-feed-cache.php is deprecated Import normal normal WordPress.org defect (bug) new 2022-10-19T20:58:34Z 2022-10-19T20:58:34Z "The Blogger Importer plugin (tested v0.9) causes the following deprecation notice: PHP Deprecated: File class-wp-feed-cache.php is deprecated since version 5.6.0 with no alternative available. This file is only loaded for backward compatibility with SimplePie 1.2.x. Please consider switching to a recent SimplePie version. in ../wp-includes/functions.php on line 5587 `class-wp-feed-cache.php` was deprecated in [49565]. " ironprogrammer Import 56856 Blogger Importer: File class-feed.php is deprecated Import normal normal WordPress.org defect (bug) new 2022-10-19T19:41:56Z 2023-11-28T22:56:10Z "The Blogger Importer plugin (tested v0.9) causes the following deprecation notice: PHP Deprecated: File class-feed.php is deprecated since version 4.7.0! Use fetch_feed() instead. in ../wp-includes/functions.php on line 5577 `class-feed.php` was deprecated in [39449]. " ironprogrammer Import 8578 Blogger import incorrectly reports saved user information Import normal normal WordPress.org defect (bug) new 2008-12-11T16:53:52Z 2019-03-15T00:30:30Z "I installed a fresh copy of WordPress 2.7 and was importing content from a Blogger site. Before beginning to import, the page claimed that Blogger account information was saved in the database and that I could restart the process. Even after pressing the ""Clear account information"" button, the message still appeared." covert215 General 60000 alot of tags is too many General normal normal WordPress.org enhancement new dev-feedback 2023-12-01T18:06:00Z 2024-01-09T16:12:22Z "[[Image(https://core.trac.wordpress.org/raw-attachment/ticket/13237/alot-of-bugs.gif)]] Previously: - #50000 - #40000 - #30000 - #20000 - #13536 - #13237 Changed with thanks to @joostdevalk. See #60001 " jorbin Upgrade/Install 43395 Add Automated E2E Tests for Core Updates Upgrade/Install normal normal WordPress.org task (blessed) new 2018-02-23T20:10:48Z 2020-03-04T11:21:34Z "This is a follow up to the issues introduced in #43103 and described in https://make.wordpress.org/core/2018/02/06/wordpress-4-9-4-release-the-technical-details/ Essentially, due to the way automated updates work, we need automated tests that can confirm they are working. Due to the code loading path differences between phpunit, wp-cli, wp-cron, and the WordPress UI, it's important that this test work as close as possible to the way the majority of sites are autoupdated. " jorbin General 53216 A Gutenberg Block repo General normal normal WordPress.org feature request new dev-feedback 2021-05-16T09:26:52Z 2023-04-20T13:38:47Z "Right now the plugin has it's repository, and the themes have one. The Gutenberg blocks are now often shipped in a plugin (and sometimes even in a theme). These plugins often ship many blocks when only one or a few are needed. This can cause bloated websites, and takes away flexibility. My suggestion is, why not an extra repo for Gutenberg blocks, or maybe even extensions in general (custom post types as well, but not super sure about that). You'd have a super easy separation of concerns: - Theme repo for styles - Plugin repo for functionality - Gutenberg(/Add-on) repo for added blocks(/types) It would then be amazing if you could choose from a few separate blocks, or if you really like a company/developer, maybe a small set of blocks that go well together. I know it sounds like a big change, but I like thinking big and I think that's what we're doing with Gutenberg anyway. We could also just clone the system for the plugin repo and only make a few adjustments. Thoughts?" tomjdevisser