Production & Streams:form

[patcouch]

I set up a very simple page that calls the following streams form and utilizes the image field type (the new ajax automated one that is in development). When set to development everything works great. However, when I switch to production everything goes stops working. The add_js & add_css files are no longer loaded once the page is cached, the return value seems to be ignored as it loads the same page no matter what, and the value is cached unless I manually clear the cache.

{{ streams:form stream="rvs" mode="edit" edit_id={ tools:get_owners_rv } creator_only="yes" include="images" return="dashboard/listing-details/4" } }} 
    {{ form_open }}
        <h3>Vehicle Information</h3>
        {{ fields }}
            <table>
                <tbody>
                    <tr class="{{ odd_even }}">
                        <td width="250">{{ input_title }}{{ required }} <small>{{ instructions }}</small></td>
                        <td>{{ error }}{{ input }}</td>
                    </tr>
            </tbody>
            </table>
        {{ /fields }} 
        <input type="submit" value="Save &amp; Continue">
    {{ form_close }} 
{{ /streams:form }} 

Any one of these bugs makes the streams:form useless for user manageable content outside the admin. I verified the issue was not due to the image upload field that is in beta, by adding a date field and I had the same issues. I tried on both my local mamp setup and on my centos server and have the exact same results.

I am using 2.2.1 pro

[patcouch]

I thought through these issues and have become more familiar with pyrocms even in the last 24 hours and I think only one of these issues is actually a real bug.

The return value in my streams:form tag does not work when I switch over to production/staging. In development the form saves and loads the page specified in the return value. However, in production/staging the form reloads to the current page no matter what changes I make to it.