Forum Replies Created

Viewing 15 replies - 1 through 15 (of 18 total)
  • Thread Starter hexified


    It’s indeed an issue with Lync but also what’s stopping a malicious person from coding up some hidden toolbars that get installed on someone’s machine and it injects code into HTML editors in a similar fashion?

    I assume there must be a way for WordPress devs to adjust the editor so that it only accepts paste commands via right-click or ctrl-v commands with some javascript?

    Is there a way to remove TinyMCE entirely, just make it a textarea but then incorporate a ‘variable type’ that adopts the characteristics of that type?

    For example if I create a variable with some text and want it to be a link, I choose “variable type: link” and it provides me with an area for URL to link to, new window/same window, etc. then upon publishing the content block it wraps the textarea in the proper “a” tags.

    if I choose variable type: text it wraps it in “p” tags. etc.

    Just an idea, otherwise I’m stumped for the time being.

    The issue I’m having is with creating the Content Block itself.

    When editing the text, if I want a content block to simply be a link with no <p> so it can be inserted in the middle of a paragraph it breaks the paragraph when the <p></p> is auto wrapped around the link.

    The default WP Editor seems to adopt TinyMCE Advanced plugin settings globally no matter what – as long as it uses the WP Editor.

    Not sure how to get around this unless this plugin has an ‘advanced config’ section that allows you to modify TinyMCE settings that only directly affect this plugin such as the root_block and p_newlines, etc.

    Removing the editor functionality totally is a mistake as I find it valuable being able to use the variables for literally anything from a movie, image, etc.

    TinyMCE Advanced conflicts with this plugin. It seems if you have the “stop showing” checked it also affects how this plugin acts in regards to <p> tags.

    Not sure how to resolve this without leaving it unchecked and using the above hack…but a proper fix needs to be done.

    the issue with this solution is now any new lines created in the editor in a global block don’t become paragraphs automatically so you have to manually create the <p> tags yourself.

    You can actually remove the “wpautop” => false, from the line as I have it commented out.

    I think I found a solution:

    in gcb.class.php where the array is set to wpautop = false I’ve changed the function at line 514 to:

    if (function_exists(‘wp_editor’)) {
    //”wpautop” => false,//we do not need auto paragraphs
    “force_p_newlines” => false,
    “force_root_block” => false,

    Having the same issue here. P tags are automatically inserted whereas they weren’t before.

    Thread Starter hexified


    Seems the issue is that when trying to edit the settings to this plugin it automatically opens the global wordpress settings menu rather than the global content block settings.

    This needs to be fixed so that I can allow editors to add/remove/edit content blocks without globally granting them access to make changes to all wordpress core settings.

    I was just going to post to ask this. I have a custom post type where I NEED this plugin to work with and it’s locked to just blog post types. Is there a way to incorporate this plugin to other post types as well?

    Thread Starter hexified


    Figured out the issue finally…

    Apparently the Rule #3 was causing for some reason ONLY small resolution jpgs to not show up in the editor properly. Once I removed that rule, it fixed the issue.

    Thread Starter hexified


    After a ton of investigation, I narrowed it down to my web.config. This is the only way I’ve managed to get my subdirectory multisites to show up properly but it apparently breaks my media library in the main site.

    <?xml version=”1.0″ encoding=”UTF-8″?>
    <rule name=”WordPress Rule 1″ stopProcessing=”true”>
    <match url=”^index\.php$” ignoreCase=”false”/>
    <action type=”None”/>
    <rule name=”WordPress Rule 2″ stopProcessing=”true”>
    <match url=”^wordpresstest/([_0-9a-zA-Z-]+/)?wp-admin$” ignoreCase=”false”/>
    <action type=”Redirect” url=”{R:1}wp-admin/” redirectType=”Permanent”/>
    <rule name=”WordPress Rule 3″ stopProcessing=”true”>
    <match url=”^” ignoreCase=”false”/>
    <conditions logicalGrouping=”MatchAny”>
    <add input=”{REQUEST_FILENAME}” matchType=”IsFile” ignoreCase=”false”/>
    <add input=”{REQUEST_FILENAME}” matchType=”IsDirectory” ignoreCase=”false”/>
    <action type=”None”/>
    <rule name=”WordPress Rule 4″ stopProcessing=”true”>
    <match url=”^wordpresstest/([_0-9a-zA-Z-]+/)?(wp-(content|admin|includes).*)” ignoreCase=”false”/>
    <action type=”Rewrite” url=”wordpresstest/{R:1}”/>
    <rule name=”WordPress Rule 5″ stopProcessing=”true”>
    <match url=”^wordpresstest/([_0-9a-zA-Z-]+/)?([_0-9a-zA-Z-]+/)?(.*\.php)$” ignoreCase=”false”/>
    <action type=”Rewrite” url=”wordpresstest/{R:2}”/>
    <rule name=”WordPress Rule 6″ stopProcessing=”true”>
    <match url=”.” ignoreCase=”false”/>
    <action type=”Rewrite” url=”index.php”/>

    Thread Starter hexified


    This also happens under the default theme with all plugins disabled. I’m running a multi-site as well if that makes a difference.

    Thread Starter hexified


    I’ve noticed the the small resolution image doesn’t get uploaded to the media library folder at all under it’s original filename which causes the broken link (it only shows multiple versions that have been resized with dimensions appended to the name but not the original file itself).

    if I upload the large resolution image, wordpress automatically sizes down the image and appends the dimension to the filename in the media library folder and links it properly.

    Thread Starter hexified


    Yes, I’ve tried all that.

    The media upload only seems to properly show the thumbnail image if you upload a large resolution image that it crops and appends the dimensions to the filename.

    If I upload a small resolution image, it doesn’t seem to automatically crop it and it shows a broken image in the edit media window.

    ie: if I upload an image 600px wide, the preview shows a broken image. if I upload the same image 1000px wide, it shows the preview fine.

Viewing 15 replies - 1 through 15 (of 18 total)