<?xml version="1.0" encoding="utf-8" ?>
<rss version="2.0"
    xmlns:dc="http://purl.org/dc/elements/1.1/"
    xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
    xmlns:admin="http://webns.net/mvcb/"
    xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
    xmlns:content="http://purl.org/rss/1.0/modules/content/">
    
    <channel>
    
    <title>ExpressionEngine Community Forums</title>
    <link>http://expressionengine.com/forums/</link>
    <description>ExpressionEngine Community Forums</description>
    <dc:language>en</dc:language>
    <dc:rights>Copyright 2008</dc:rights>
    <dc:date>2008-07-19T16:46:00-06:00</dc:date>
    <admin:generatorAgent rdf:resource="http://www.pmachine.com/" />
    

    <item>
      <title>$100 for an EE CP iPhone app (and/or an alternate CAPTCHA system)</title>
      <link>http://expressionengine.com/forums/viewthread/85424/</link>
      <guid>http://expressionengine.com/forums/viewthread/85424/#When:21:03:07Z</guid>
      <description>&lt;p&gt;all I actually need is a way to moderate blog comments via my iPhone.
&lt;br /&gt;
$25 bonus if the app pings me in the background(!) when new comments are posted &lt;img src=&quot;http://ellislab.com/images/smileys/grin.gif&quot; width=&quot;19&quot; height=&quot;19&quot; alt=&quot;grin&quot; style=&quot;border:0;&quot; /&gt;
&lt;/p&gt;
&lt;p&gt;
seriously (actually, I&#8217;m willing to pay that money!!), it would be nice if there was another type of captcha, like the human&#45;response question thing where the comment form asks &#8220;what is 5*4&#8221; or something&#8230; anytyhing that will help prevent spam comments. 
&lt;/p&gt;
&lt;p&gt;
thanks
&lt;br /&gt;
=p
&lt;/p&gt;</description>
      <dc:date>2008-07-16T21:03:07-06:00</dc:date>
    </item>

    <item>
      <title>CP &amp;gt; Publish &amp;gt; Choose weblog to publish in</title>
      <link>http://expressionengine.com/forums/viewthread/85697/</link>
      <guid>http://expressionengine.com/forums/viewthread/85697/#When:13:51:58Z</guid>
      <description>&lt;p&gt;Add &#8220;to the choose weblog to publish in&#8221; form and dorp down menu in the CP the ability to display the back_end_description of the weblog along with its name and the ability to enter a back_end_description when creating or editing weblogs.
&lt;/p&gt;
&lt;p&gt;
Sometimes when we assign a name to a weblog, it is not always apparent what the intended use of the weblog is.&amp;nbsp; We may have named a weblog which makes perfect sense within the context of where its name is used within templates in the front end but isn&#8217;t as clear within the back end when listed just by name; or in some instances where a weblog may be used for something other than regular entries.&amp;nbsp; This would allow the use and display of the back_end_description to assist in selecting the correct weblog to post in.
&lt;/p&gt;
&lt;p&gt;
Does this make sense?&amp;nbsp; I think logically it will require a new field in the weblogs table and coding and settings to support.
&lt;/p&gt;</description>
      <dc:date>2008-07-19T13:51:58-06:00</dc:date>
    </item>

    <item>
      <title>Gallery Category names in URL</title>
      <link>http://expressionengine.com/forums/viewthread/63948/</link>
      <guid>http://expressionengine.com/forums/viewthread/63948/#When:17:00:29Z</guid>
      <description>&lt;p&gt;On my site I have two sub&#45;categories, September and October. I want to be able to type something like ‘http://thedalzells.org/gallery/category/October’ and have the October (cat id ‘C2’) show up.
&lt;/p&gt;</description>
      <dc:date>2007-10-30T17:00:29-06:00</dc:date>
    </item>

    <item>
      <title>Pagination links class</title>
      <link>http://expressionengine.com/forums/viewthread/85576/</link>
      <guid>http://expressionengine.com/forums/viewthread/85576/#When:07:24:45Z</guid>
      <description>&lt;p&gt;I came across some simple idea : add class to pagination links. It&#8217;s very simple to do : edit core.pagination.php and add class=&quot;className&quot; to each type of links&#8221;.
&lt;/p&gt;
&lt;p&gt;
I suggest :
&lt;br /&gt;
&lt;/p&gt;&lt;div class=&quot;codeblock&quot;&gt;&lt;code&gt;
&lt;span style=&quot;color: #0000BB&quot;&gt;$output &lt;/span&gt;&lt;span style=&quot;color: #007700&quot;&gt;.= &lt;/span&gt;&lt;span style=&quot;color: #0000BB&quot;&gt;$this&lt;/span&gt;&lt;span style=&quot;color: #007700&quot;&gt;&#45;&amp;gt;&lt;/span&gt;&lt;span style=&quot;color: #0000BB&quot;&gt;first_div_o&lt;/span&gt;&lt;span style=&quot;color: #007700&quot;&gt;.&lt;/span&gt;&lt;span style=&quot;color: #DD0000&quot;&gt;&apos;&amp;lt;a &amp;gt;suffix.&apos;&quot; class=&quot;&lt;/span&gt;&lt;span style=&quot;color: #0000BB&quot;&gt;first_page&lt;/span&gt;&lt;span style=&quot;color: #DD0000&quot;&gt;&quot;&amp;gt;&apos;.$this&#45;&amp;gt;first_page.&apos;&amp;lt;/a&amp;gt;&apos;.$this&#45;&amp;gt;first_div_c; // First page pagination link&lt;br /&gt;$output .= $this&#45;&amp;gt;prev_div_o.&apos;&amp;lt;a &amp;gt;prefix.$i.$slash.$this&#45;&amp;gt;suffix.&apos;&quot;&lt;/span&gt;&lt;span style=&quot;color: #007700&quot;&gt;&amp;gt;&lt;/span&gt;&lt;span style=&quot;color: #DD0000&quot;&gt;&apos;.$this&#45;&amp;gt;prev_link.&apos;&lt;/span&gt;&lt;span style=&quot;color: #007700&quot;&gt;&amp;lt;/&lt;/span&gt;&lt;span style=&quot;color: #0000BB&quot;&gt;a&lt;/span&gt;&lt;span style=&quot;color: #007700&quot;&gt;&amp;gt;&lt;/span&gt;&lt;span style=&quot;color: #DD0000&quot;&gt;&apos;.$this&#45;&amp;gt;prev_div_c;&lt;br /&gt; // Previous pagination link&lt;br /&gt;$output .= $this&#45;&amp;gt;cur_div_o.&apos;&lt;/span&gt;&lt;span style=&quot;color: #007700&quot;&gt;&amp;lt;&lt;/span&gt;&lt;span style=&quot;color: #0000BB&quot;&gt;b&lt;/span&gt;&lt;span style=&quot;color: #007700&quot;&gt;&amp;gt;&lt;/span&gt;&lt;span style=&quot;color: #DD0000&quot;&gt;&apos;.$loop.&apos;&lt;/span&gt;&lt;span style=&quot;color: #007700&quot;&gt;&amp;lt;/&lt;/span&gt;&lt;span style=&quot;color: #0000BB&quot;&gt;b&lt;/span&gt;&lt;span style=&quot;color: #007700&quot;&gt;&amp;gt;&lt;/span&gt;&lt;span style=&quot;color: #DD0000&quot;&gt;&apos;.$this&#45;&amp;gt;cur_div_c; // Current page&lt;br /&gt;$output .= $this&#45;&amp;gt;num_div_o.&apos;&lt;/span&gt;&lt;span style=&quot;color: #007700&quot;&gt;&amp;lt;&lt;/span&gt;&lt;span style=&quot;color: #0000BB&quot;&gt;a &lt;/span&gt;&lt;span style=&quot;color: #007700&quot;&gt;&amp;gt;&lt;/span&gt;&lt;span style=&quot;color: #0000BB&quot;&gt;prefix&lt;/span&gt;&lt;span style=&quot;color: #007700&quot;&gt;.&lt;/span&gt;&lt;span style=&quot;color: #0000BB&quot;&gt;$i&lt;/span&gt;&lt;span style=&quot;color: #007700&quot;&gt;.&lt;/span&gt;&lt;span style=&quot;color: #0000BB&quot;&gt;$slash&lt;/span&gt;&lt;span style=&quot;color: #007700&quot;&gt;.&lt;/span&gt;&lt;span style=&quot;color: #0000BB&quot;&gt;$this&lt;/span&gt;&lt;span style=&quot;color: #007700&quot;&gt;&#45;&amp;gt;&lt;/span&gt;&lt;span style=&quot;color: #0000BB&quot;&gt;suffix&lt;/span&gt;&lt;span style=&quot;color: #007700&quot;&gt;.&lt;/span&gt;&lt;span style=&quot;color: #DD0000&quot;&gt;&apos;&quot; class=&quot;pagination_link&quot;&amp;gt;&apos;&lt;/span&gt;&lt;span style=&quot;color: #007700&quot;&gt;.&lt;/span&gt;&lt;span style=&quot;color: #0000BB&quot;&gt;$loop&lt;/span&gt;&lt;span style=&quot;color: #007700&quot;&gt;.&lt;/span&gt;&lt;span style=&quot;color: #DD0000&quot;&gt;&apos;&amp;lt;/a&amp;gt;&apos;&lt;/span&gt;&lt;span style=&quot;color: #007700&quot;&gt;.&lt;/span&gt;&lt;span style=&quot;color: #0000BB&quot;&gt;$this&lt;/span&gt;&lt;span style=&quot;color: #007700&quot;&gt;&#45;&amp;gt;&lt;/span&gt;&lt;span style=&quot;color: #0000BB&quot;&gt;num_div_c&lt;/span&gt;&lt;span style=&quot;color: #007700&quot;&gt;; &lt;/span&gt;&lt;span style=&quot;color: #FF8000&quot;&gt;// Classic pagination link&lt;br /&gt;&lt;/span&gt;&lt;span style=&quot;color: #0000BB&quot;&gt;$output &lt;/span&gt;&lt;span style=&quot;color: #007700&quot;&gt;.= &lt;/span&gt;&lt;span style=&quot;color: #0000BB&quot;&gt;$this&lt;/span&gt;&lt;span style=&quot;color: #007700&quot;&gt;&#45;&amp;gt;&lt;/span&gt;&lt;span style=&quot;color: #0000BB&quot;&gt;next_div_o&lt;/span&gt;&lt;span style=&quot;color: #007700&quot;&gt;.&lt;/span&gt;&lt;span style=&quot;color: #DD0000&quot;&gt;&apos;&amp;lt;a &amp;gt;prefix.($this&#45;&amp;gt;cur_page * $this&#45;&amp;gt;per_page).$slash.$this&#45;&amp;gt;suffix.&apos;&quot; class=&quot;&lt;/span&gt;&lt;span style=&quot;color: #0000BB&quot;&gt;next_link&lt;/span&gt;&lt;span style=&quot;color: #DD0000&quot;&gt;&quot;&amp;gt;&apos;.$this&#45;&amp;gt;next_link.&apos;&amp;lt;/a&amp;gt;&apos;.$this&#45;&amp;gt;next_div_c; // Next pagination link&lt;br /&gt;$output .= $this&#45;&amp;gt;last_div_o.&apos;&amp;lt;a &amp;gt;prefix.$i.$slash.$this&#45;&amp;gt;suffix.&apos;&quot; &lt;/span&gt;&lt;span style=&quot;color: #007700&quot;&gt;class=&lt;/span&gt;&lt;span style=&quot;color: #DD0000&quot;&gt;&quot;last_page&quot;&lt;/span&gt;&lt;span style=&quot;color: #007700&quot;&gt;&amp;gt;&lt;/span&gt;&lt;span style=&quot;color: #DD0000&quot;&gt;&apos;.$this&#45;&amp;gt;last_page.&apos;&lt;/span&gt;&lt;span style=&quot;color: #007700&quot;&gt;&amp;lt;/&lt;/span&gt;&lt;span style=&quot;color: #0000BB&quot;&gt;a&lt;/span&gt;&lt;span style=&quot;color: #007700&quot;&gt;&amp;gt;&apos;&lt;/span&gt;&lt;span style=&quot;color: #0000BB&quot;&gt;.$this&#45;&amp;gt;last_div_c; // Last pagination link&lt;/span&gt;
&lt;/code&gt;&lt;/div&gt;&lt;p&gt; 
&lt;/p&gt;
&lt;p&gt;
It would be great to change current page&#8217;s tag from &amp;lt;b&amp;gt; to &amp;lt;div&amp;gt; for example in order to let it be stylable : &amp;lt;b&amp;gt; tag doesn&#8217;t support background img for example.
&lt;/p&gt;
&lt;p&gt;
Simple improvement for great customisation option ! Hope this may help &lt;img src=&quot;http://ellislab.com/images/smileys/smile.gif&quot; width=&quot;19&quot; height=&quot;19&quot; alt=&quot;smile&quot; style=&quot;border:0;&quot; /&gt;
&lt;/p&gt;</description>
      <dc:date>2008-07-18T07:24:45-06:00</dc:date>
    </item>

    <item>
      <title>templates across modules and plugins</title>
      <link>http://expressionengine.com/forums/viewthread/85293/</link>
      <guid>http://expressionengine.com/forums/viewthread/85293/#When:16:45:22Z</guid>
      <description>&lt;p&gt;Hello,
&lt;/p&gt;
&lt;p&gt;
It would be great if the templates for the forum and other modules were housed in the main EE templates area, and if you could simply use EE tags within them. It would simplify everything. It would be just another template set in there. I have my fingers crossed that the new version of ee has all the tags available within any of the templates.
&lt;/p&gt;</description>
      <dc:date>2008-07-15T16:45:22-06:00</dc:date>
    </item>

    <item>
      <title>Doc improvement suggestions</title>
      <link>http://expressionengine.com/forums/viewthread/85485/</link>
      <guid>http://expressionengine.com/forums/viewthread/85485/#When:10:21:33Z</guid>
      <description>&lt;p&gt;Following a discussion &lt;a href=&quot;http://expressionengine.com/forums/viewthread/85208/&quot;&gt;that went a bit astray&lt;/a&gt; and a quick exchange of email with Derek who suggested I share my views on doc improvement here. I have many suggestions actually, but I&#8217;ll go for what I believe is the most glaring omission in the current doc.
&lt;/p&gt;
&lt;p&gt;
This is offered in the spirit of trying to improve on what I consider a good product. And I appreciate that you have priorities in the development and cannot address all the feature requests.
&lt;/p&gt;
&lt;p&gt;
In the original discussion, Derek correctly points that it is not possible for the documentation to anticipate the needs of all the users. There is however a simple technique around that problem: give the reader enough information to build a reliable mental model of how the software works. This allows someone to infer how (s)he can use the software in novel ways.
&lt;/p&gt;
&lt;p&gt;
Actually the doc does that in one place: when it describes the relationship between weblogs, custom fields and templates. It is not possible to describe every possible use so instead it describes the underlying generic mechanism and gives a few example which allows the user to build a mental model and decide for itself how to use it in different context.
&lt;/p&gt;
&lt;p&gt;
The same solution could be used efficiently to describe the parsing, database model, caching, and some other aspects. I have surfed this forum pretty extensively in the last few months as I was trying to use all the ressources to build said mental model and it is my belief that many questions that are being raised here could be addressed once and for all with proper documentation.
&lt;/p&gt;
&lt;p&gt;
Many company offer this layer of documentation as tech notes.
&lt;/p&gt;</description>
      <dc:date>2008-07-17T10:21:33-06:00</dc:date>
    </item>

    <item>
      <title>User Message Templates don&#8217;t work with JavaScript Disabled.</title>
      <link>http://expressionengine.com/forums/viewthread/85472/</link>
      <guid>http://expressionengine.com/forums/viewthread/85472/#When:09:16:05Z</guid>
      <description>&lt;p&gt;I think it would be preferable if the &#8216;User Message&#8217; templates worked without JavaScript enabled.
&lt;/p&gt;
&lt;p&gt;
At present the &#8216;Return to Previous Page&#8217; link is written as a JavaScript history back&#45;1, is there any reason for this? Could EE not get the referring URL instead, or at least use JavaScript in an unobtrusive manner?
&lt;/p&gt;
&lt;p&gt;
&lt;/p&gt;&lt;div class=&quot;codeblock&quot;&gt;&lt;code&gt;
&lt;span style=&quot;color: #007700&quot;&gt;&amp;lt;&lt;/span&gt;&lt;span style=&quot;color: #0000BB&quot;&gt;a href&lt;/span&gt;&lt;span style=&quot;color: #007700&quot;&gt;=&lt;/span&gt;&lt;span style=&quot;color: #DD0000&quot;&gt;&quot;http://www.referringurl.com&quot;&lt;/span&gt;&lt;span style=&quot;color: #007700&quot;&gt;&amp;gt;Return &lt;/span&gt;&lt;span style=&quot;color: #0000BB&quot;&gt;to Previous Page&lt;/span&gt;&lt;span style=&quot;color: #007700&quot;&gt;&amp;lt;/&lt;/span&gt;&lt;span style=&quot;color: #0000BB&quot;&gt;a&lt;/span&gt;&lt;span style=&quot;color: #007700&quot;&gt;&amp;gt;&lt;/span&gt;
&lt;/code&gt;&lt;/div&gt;&lt;p&gt;
&lt;/p&gt;
&lt;p&gt;
The href of the link could be returned as the ref URL and then the JavaScript could be applied as an onClick meaning that with JavaScript disabled the link would still function as expected.
&lt;/p&gt;
&lt;p&gt;
:?
&lt;/p&gt;</description>
      <dc:date>2008-07-17T09:16:05-06:00</dc:date>
    </item>

    <item>
      <title>SEFURL &#45; For the Forum + Sitemap &#45; SEO</title>
      <link>http://expressionengine.com/forums/viewthread/85452/</link>
      <guid>http://expressionengine.com/forums/viewthread/85452/#When:05:40:51Z</guid>
      <description>&lt;p&gt;Hey,
&lt;/p&gt;
&lt;p&gt;
I thought it would be great for the next version of ExpressionEngine and the Forum module &#45; Was to be able to create a Sitemap for all articles/blogs and Forum topics/members etc.
&lt;/p&gt;
&lt;p&gt;
Also what I think the forum is lacking is having Search Engien Friendly URL&#8217;s &#45; having this implemented would really help increase traffic to the forum, is this something you could think about implementing?
&lt;/p&gt;
&lt;p&gt;
e.g.
&lt;/p&gt;
&lt;p&gt;
So  /forums/newtopic/9/
&lt;/p&gt;
&lt;p&gt;
Would become /forums/category_name/topic_title.html
&lt;/p&gt;
&lt;p&gt;
Many thanks.
&lt;/p&gt;</description>
      <dc:date>2008-07-17T05:40:51-06:00</dc:date>
    </item>

    <item>
      <title>FR: Forum post SPLIT</title>
      <link>http://expressionengine.com/forums/viewthread/85415/</link>
      <guid>http://expressionengine.com/forums/viewthread/85415/#When:18:20:46Z</guid>
      <description>&lt;p&gt;Its very silly that i have first create a new thread &#45; then go to some other thread and hit merge&#45;button or move&#45;button instead of just using very forum&#45;common split&#45;feature for separating replies to their own threads.
&lt;/p&gt;
&lt;p&gt;
So hopefully this comes around.
&lt;/p&gt;
&lt;p&gt;
Thanks:
&lt;br /&gt;
&#45; Tuittu
&lt;/p&gt;</description>
      <dc:date>2008-07-16T18:20:46-06:00</dc:date>
    </item>

    <item>
      <title>More than one group per member&#63;</title>
      <link>http://expressionengine.com/forums/viewthread/85412/</link>
      <guid>http://expressionengine.com/forums/viewthread/85412/#When:17:27:55Z</guid>
      <description>&lt;p&gt;I looked around but could not find this. This is a very essential part of many web communities and has bugged me about EE. Is there a way to assign a member to more than one group now or do we still have to create unique hybrid groups for one or two people that might happen to overlap a couple of duties?
&lt;/p&gt;
&lt;p&gt;
I would like to see this feature very much. If it is already available, I can&#8217;t seem to find it.
&lt;/p&gt;
&lt;p&gt;
Thanks!
&lt;/p&gt;</description>
      <dc:date>2008-07-16T17:27:55-06:00</dc:date>
    </item>

    
    </channel>
</rss>