Posts Tagged ‘expression engine’

EE Users post with status Closed

Posted in Ramblings, Websites on April 22nd, 2009 by Jason – Be the first to comment

I recently had a problem where all the users added to expression engine would post to weblogs with a closed status and they did not have the option to change it to open even though they had permissions to do so. It took me a while to figure this one out, but like many things with expression engine, I have found that their are simple solutions to almost all of the issues that I have found, it was just a matter of finding the solutions.

If your having problems with other members publishing as closed status and cant figure out why, try checking the following setting. Select publish and then edit weblogs. For the weblog that you are having problems with, and this could be all of them, you will need to select to edit groups, and from there you will need to make sure that the default option is NOT None, but set to either the Default Status Group or a custom one.

Default Status Group

Post to Twitter Tweet This Post

Quick EE tip, RSS feed not working

Posted in Ramblings, Websites on April 22nd, 2009 by Jason – Be the first to comment

This is not so much a tip for what to do but what not to do. I recently had an RSS page that was giving some strange errors in expression engine. The fix was simple, when you create your template, make sure you select it to be an RSS page. Seems simple enough, but if you select it to be a webpage, everything will look as it should with the exception of just one thing.

When I created the template, I would get the following error in the safari web browser, and would not get results in other web browsers.

The error was: “The feed could not be loaded because the content is not in a known feed format.” (PubSub:2)

After looking at the source code, the only thing that I could see which was different than that of a standard RSS feed was the following line of code.

<ee:last_update>

Why expression engine adds that line, I dont know, but if you see this, be sure to check that your template is set to be an RSS template and not a webpage.

Post to Twitter Tweet This Post