a followup page ([next_page_slug]/'After donating, what page should they land on next?') to a donation page inserts the follow-up page's url in its facetweet instead of the donation page's url -- could there be a setting for followup pages to refer to the referring donation form? or just make that the default?
Previewing (layout_autoresponse.html) always loads a site's home page for us -- can this be fixed?Official response from Adriel Hampton considering
Ron, have you seen the new "report a problem" link in the control panel footer? Reporting your issue there will put it directly in the hands of our engineers for review (along with giving them additional bug troubleshooting info from the page and browser).
When a user signs a petition (or completes another action), we can tag him/her (as, say, petition_signer), but if s/he unsigns that petition (or otherwise undo the action), the tag (petition_signer) remains. Since the "on action" tags exist solely to track actions, shouldn't those tags be tied to the users' status for that action? (eg, when a user unsigns a petition, his/her petition_signer tag should zap itself.)
when listing child pages, what's the syntax for sorting by date? the default date sort seems to be based on child page modification date and adding a sort (for page in page.children sort:published_at) doesn't override the default sort. anyone have any luck with this?Official response from Drew Cross
While things like blog posts and calendar events will always be displayed in chronological order, subpages will generally be listed with the most recently modified near the top of the 'Active pages' list in the control panel. However, if these subpages are included in a top nav, the default order is based on published date, with the most recently published being at the top. In these situation, the "Sub nav pages" tab will allow you to click and drag the pages in to the order you want.
We get lots of request from clients to make certain fields required. It would be great if most/all text fields would either accept a 'required' parameter at the template level or have a 'required' checkbox in that form's settings.
We understand. philosphically, why more fields are not currently required, but not all of our clients do.
Placing a youtube vide w/embed.ly snippet: renders great w/ http, doesn't render w/https. The video is for a donation page--we need https. Sure we can embed the video in the template, but that's no fun. Can embed.ly be configured to supprt https?
Presenting past petitions (alliteration, anyone?) is a great way for an org to demonstrate efficacy, but, without a template edit, there's no way to display a petition without also allowing users to sign it. A "closed" checkbox would be very handy.