New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[if] Shortcode Pro v170220.78352-RC #3
Comments
Tested
|
Should the notes regarding JetPack and Markdown be more visible? Such as a note underneath the option, rather than in the question mark pop-up? I feel like more casual users would miss this note. :) Also, was unable to find WP Markdown Extra as a plugin, but according to Jetpack, it utilizes it as a Writing Option.
|
@jaswsinc @raamdev Everything seems to be working great. No bugs to report, is there anything else I should test specifically for failure? The Markdown Extra + Jetpack support work awesome. Markdown Extra + Jetpack Back End Shortcode Front end logged-in Front end logged-out This works for both conditions of Jetpack / Markdown Extra support since Markdown Extra is integrated with Jetpack. When the option is off, Markdown is only supported outside the |
@renzms Thanks for the testing! That's all we need. :-) I'll put out a GA release soon. |
Republishing this RC, as I forgot to follow up here with a GA release. See #4. |
Downloads
Please see the download links in Slack:
https://websharks.slack.com/archives/if-shortcode/p1487627335000012
Changelog
v170220.78352-RC
wp-markdown-extra
filter configuration.WP_Hook
class addresses the underlying problem this was solving. See Issue #1.basename(__FILE__)
from direct access notices..build.props
file.Reporting Issues / Feedback
Please report any issues or feedback related to this Release Candidate using this GitHub issue. Please post a comment below with details.
If you are reporting a UI-related issue, please include a screenshot.
If you are reporting a bug, please provide list of steps to reproduce and if the bug is related to an existing GitHub issue, please provide a link to that GitHub issue as well.
Reported Issues to Fix
None at this time.
The text was updated successfully, but these errors were encountered: