<?xml version="1.0" encoding="UTF-8"?>
<!-- generator="bbPress/1.1" -->
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
		>
	<channel>
		<title>WordPress Ideas &#187; Forum: Editing - Recent Posts</title>
		<link>https://wordpress.org/ideas/forum/editing</link>
		<description>WordPress Ideas &#187; Forum: Editing - Recent Posts</description>
		<language>en-US</language>
		<pubDate>Fri, 09 Jun 2017 13:16:35 +0000</pubDate>
		<generator>http://bbpress.org/?v=1.1</generator>
				<atom:link href="https://wordpress.org/ideas/rss/forum/editing" rel="self" type="application/rss+xml" />

		<item>
			<title>parkerlightroompresets on "Embed Menus Within Menus"</title>
			<link>https://wordpress.org/ideas/topic/embed-menus-within-menus#post-31919</link>
			<pubDate>Mon, 05 Jun 2017 17:35:21 +0000</pubDate>
			<dc:creator>parkerlightroompresets</dc:creator>
			<guid isPermaLink="false">31919@https://wordpress.org/ideas/</guid>
			<description><![CDATA[<p>Not sure if this idea is still "active" but as far as I know it hasn't been implemented, right?</p>
<p>This would be a very useful feature even tough I am not always a fan of super big menues because it might affect the user experience.</p>
<p>Nevertheless I am in need for this feature for a current client. I am using the Mega Menue Plugin to build in depth and visual structures. A out of the box option in WP would be great.
</p>]]></description>
					</item>
		<item>
			<title>stefan3566 on "[editing] Speech to text editor"</title>
			<link>https://wordpress.org/ideas/topic/editing-speech-to-text-editor#post-31903</link>
			<pubDate>Thu, 01 Jun 2017 14:45:57 +0000</pubDate>
			<dc:creator>stefan3566</dc:creator>
			<guid isPermaLink="false">31903@https://wordpress.org/ideas/</guid>
			<description><![CDATA[<p>Hello!<br />
How about integrating a speech to text-possibility into wordpress for easier editing?</p>
<p>[redacted]
</p>]]></description>
					</item>
		<item>
			<title>chasman on "Ability to select Private Page as Parent"</title>
			<link>https://wordpress.org/ideas/topic/ability-to-select-private-page-as-parent/page/3#post-31846</link>
			<pubDate>Sat, 13 May 2017 16:44:03 +0000</pubDate>
			<dc:creator>chasman</dc:creator>
			<guid isPermaLink="false">31846@https://wordpress.org/ideas/</guid>
			<description><![CDATA[<p>The CMS Tree View plugin is excellent and I use it all the time. However, the default WordPress behaviour is the problem. If you edit any child node of a private parent the child's parent is immediately set to (no parent) because the dropdown doesn't have it as a valid value.</p>
<p><a href="https://www.evernote.com/l/AAKqUUp2m7VNPq-_J12EOVOc2lUePXs6eVYB/image.png" rel="nofollow">https://www.evernote.com/l/AAKqUUp2m7VNPq-_J12EOVOc2lUePXs6eVYB/image.png</a></p>
<p><a href="https://www.evernote.com/l/AAICIX9olOVKw7_LiloqWiyMwV5VyB1QlCYB/image.png" rel="nofollow">https://www.evernote.com/l/AAICIX9olOVKw7_LiloqWiyMwV5VyB1QlCYB/image.png</a>
</p>]]></description>
					</item>
		<item>
			<title>luciandavidescu on "Unlisted posts"</title>
			<link>https://wordpress.org/ideas/topic/unlisted-posts/page/2#post-31788</link>
			<pubDate>Fri, 28 Apr 2017 16:23:19 +0000</pubDate>
			<dc:creator>luciandavidescu</dc:creator>
			<guid isPermaLink="false">31788@https://wordpress.org/ideas/</guid>
			<description><![CDATA[<p>This is a good candidate for core, I think.<br />
It makes sense to hide posts that are no longer relevant but reference or for a very long-tail search - so it's a different thing from noindexing. Anyway, it's more useful than a private post.<br />
Lots of websites/themes are already doing it in all sorts  of suboptimal ways. As soon as the theme is changed, functionality becomes broken and has to be done all over again.
</p>]]></description>
					</item>
		<item>
			<title>mannui on "Improved Visual Editor"</title>
			<link>https://wordpress.org/ideas/topic/improved-visual-editor/page/12#post-31785</link>
			<pubDate>Thu, 27 Apr 2017 04:54:30 +0000</pubDate>
			<dc:creator>mannui</dc:creator>
			<guid isPermaLink="false">31785@https://wordpress.org/ideas/</guid>
			<description><![CDATA[<p>hi this is mannui, this plugin is very good i'm using this plugin in my blog <a href="https://downloaddrasticapk.com" rel="nofollow">https://downloaddrasticapk.com</a> you check from here
</p>]]></description>
					</item>
		<item>
			<title>Ipstenu (Mika Epstein) on "wysiwyg Editor in Categories"</title>
			<link>https://wordpress.org/ideas/topic/wysiwyg-editor-in-categories#post-31777</link>
			<pubDate>Mon, 24 Apr 2017 22:17:07 +0000</pubDate>
			<dc:creator>Ipstenu (Mika Epstein)</dc:creator>
			<guid isPermaLink="false">31777@https://wordpress.org/ideas/</guid>
			<description><![CDATA[<p>This is a question for WooCommerce, not WordPress core.</p>
<p><a href="https://wordpress.org/support/plugin/woocommerce" rel="nofollow">https://wordpress.org/support/plugin/woocommerce</a>
</p>]]></description>
					</item>
		<item>
			<title>drohne on "wysiwyg Editor in Categories"</title>
			<link>https://wordpress.org/ideas/topic/wysiwyg-editor-in-categories#post-31771</link>
			<pubDate>Sun, 23 Apr 2017 22:28:00 +0000</pubDate>
			<dc:creator>drohne</dc:creator>
			<guid isPermaLink="false">31771@https://wordpress.org/ideas/</guid>
			<description><![CDATA[<p>I use WordPress and Woocommerce and if i create an Categorie and want to edit the Content, there is just a simple textfield. Why this field is not a wysiwyg field? This will be a very useful feature for me. And another thing: If there are Products in Woocommerce and i fill something in the textfield under Categories, the text is above the products. It will be usefull too, that there a second textfield which display under the products.</p>
<p>Hope you understand me and sorry for my english i am from germany</p>
<p>Best regards
</p>]]></description>
					</item>
		<item>
			<title>failversprechend on "Frontend publishing like medium.com"</title>
			<link>https://wordpress.org/ideas/topic/frontend-publishing-like-mediumcom/page/2#post-31757</link>
			<pubDate>Tue, 18 Apr 2017 18:02:29 +0000</pubDate>
			<dc:creator>failversprechend</dc:creator>
			<guid isPermaLink="false">31757@https://wordpress.org/ideas/</guid>
			<description><![CDATA[<p>Actually i am guite happy with how wordpress works. It would be nice to have some sort of frontend publishing though. But it is no must have in my opinion.
</p>]]></description>
					</item>
		<item>
			<title>Ipstenu (Mika Epstein) on "&quot;Hidden&quot; Page Visibility"</title>
			<link>https://wordpress.org/ideas/topic/hidden-page-visibility/page/4#post-31731</link>
			<pubDate>Fri, 14 Apr 2017 23:23:44 +0000</pubDate>
			<dc:creator>Ipstenu (Mika Epstein)</dc:creator>
			<guid isPermaLink="false">31731@https://wordpress.org/ideas/</guid>
			<description><![CDATA[<p>Just to clarify one thing, and please note I'm not saying NO to this, I'm just trying to explain WordPress :)</p>
<blockquote><p>Plugins are great for extra things that don't need to be integrated.</p></blockquote>
<p>Plugins are great for extra things that may not necessarily have mass-adoption because of a limited user base.</p>
<p>But also... Plugins are great to experiment and adapt features that may later be added to core. See the Rest API, Menus, and the MP6 redesign.</p>
<p>So please, don't dismiss the plugin. If a plugin is REALLY good, it may end up in core. Use the plugin. The more people who use it, the more obvious it becomes as to what's needed. :)
</p>]]></description>
					</item>
		<item>
			<title>sondrakinsey on "&quot;Hidden&quot; Page Visibility"</title>
			<link>https://wordpress.org/ideas/topic/hidden-page-visibility/page/4#post-31727</link>
			<pubDate>Fri, 14 Apr 2017 16:50:26 +0000</pubDate>
			<dc:creator>sondrakinsey</dc:creator>
			<guid isPermaLink="false">31727@https://wordpress.org/ideas/</guid>
			<description><![CDATA[<p>I agree that this should be included in core rather than plugin for several reasons:</p>
<ol>
<li>This is a common need. In addition to the use cases Graham Stoney <a href="https://wordpress.org/ideas/topic/hidden-page-visibility#post-18293">described</a>, I would add several others:
<ul>
<li>Landing pages after user actions, eg. a thank you page after users fill out a web form.</li>
<li>Custom error pages</li>
</ul>
</li>
<li>This information would be used by many other plugins.
<p>Plugins are great for extra things that don't need to be integrated. For example, the AMP plugin adds additional functionality to your site. Most other plugins aren't impacted by your installation of AMP.</p>
<p>The page visibility status is used by many other plugins.
</li>
<li>This will significantly improve user experience for these use cases. Others have pointed out that similar functionality is possible and the various how-to pages describing this. However, the complexity of this work is obvious in the how-to pages, and even then there may be other plugins that are missed.</li>
<li>This shouldn't be hard to implement, the visibility attribute of pages already exists.</li>
</ol>
<ol></ol>]]></description>
					</item>

	</channel>
</rss>
