Cycles

Fixed the timestamp issue this in the latest version, v1.5, moving from UTC to “local time” as defined by your WordPress settings.

Hi Mark – just to close this out (we talked via email a while back), commenting inside audio and video aren’t on the roadmap, unfortunately.

If you were using Cycles for Websites (in beta) you could embed audio/video) and annotate / approve that page, but I think your needs are more sophisticated. ??

Thanks for taking the time to share your ideas! We happen to be working on a few of them for an upcoming release…:)

Thanks again for the feedback – here’s how we handled (or why we didn’t) each request, as of V1.4:

1. Responsive Option We opted for simplicity over fidelity for mockups so defaulted to a responsive view of the uploaded image (only as large as 100%), and adjusted the feedback dots to position themselves relative to the spot on the image.

2. Logged in user name: Because we’re attempting to design for cases where clients aren’t required to have accounts, we solved the “repetitive name typing” by defaulting to the most recent name (and added a dropdown to select other names or “new name”.

3. PDF support or handling: We’re looking at PDF support, but added supported image types to the documentation and readme.txt in the meantime.

4. Roles & Approvals:: V1.4 introduces an “approval” feature for any design, so anyone with access to the design URL (if it’s password protected) can approve the design.

Hope those enhancements make cycles useful to you, thanks again for the feedback.

This was fixed in v1.1, but please re-post if you see any more issues.

Oh, please take a look, I had pushed a new version literally 10 minutes before responding to your post. 1.1 came out 5 hours ago! ??

Thanks for the feature requests, Joff. We’re working on some new features that should address some of your requests. I”ll update the thread when I have more details!

If you’re willing to beta-test some of these new features, send me an email @ [email protected]. ??

Thanks for the note – I think we have this fixed in our latest version (v1.1), where we added the Post Visibility options (private, password protected, public) to the Design post type.

Please let me know if you continue to see strange button behavior, otherwise I”ll mark resolved in a few days.

Thanks for the feedback, Jesse – we just released v1.1 with password protection, so I’m going to mark resolved.

Thanks for the feedback, Jesse – yes, the use of a custom post type has some tradeoffs, but ultimately we’ve found it to be the safest route, least likely to interfere with other plugins and configurations. Password protection and unique/randomized links are on the list for future versions. ??

You mention this, but for others reading, chances are your XML Sitemap plugin is including all custom post types by default, so you can disable designs from being auto-listed.

Here’s the setting in YOAST SEO: XML Sitemap Settings Screenshot

Thanks again – appreciate the comment. I’ll mark resolved if I don’t hear back in a few days.

Thank you, too! Please let me know if there’s anything we can do to make it more useful in the future.