@test success
now you are able to create article from frontend as per #3087 on postgresql

After applying the patch in mysql and submitting an article on the front end I got the following error BUT the article was saved

This comment was created with the J!Tracker Application at issues.joomla.org/joomla-cms/5230.

In postgres pressing save just gives me an empty content form again with no error or success message but the article is created

This comment was created with the J!Tracker Application at issues.joomla.org/joomla-cms/5230.

OK from a code review/very quick physical test the error in mysql is unrelated to this and occurs when you create a duplicate alias for an item. The string exists in the backend as Alias already existed so a number was added at the end. You can re-edit the article to customise the alias which would tie in with this fact. I can replicate this without my patch applied so I would call it "unrelated" (although I guess it should be fixed for 3.4). Gonna try and figure out why no messages at all in postgres now :)

OK Really nice spot Brian! Turns out I'd missed although the article was being created the assets were not because the rules field was blank. This is fixed now. Please test again :)

@test Successful. I was able to submit and edit an article from the front-end. I also confirmed that doing the same from the back-end still works. I even tried playing around with ACLs in the front-end and back-end. Postgres 9.3.5.2 (through Postgress.app) on Mac OS X Yosemite. Great job, George!

@test all good now - setting RTC

This comment was created with the J!Tracker Application at issues.joomla.org/joomla-cms/5230.