Thread

I am trying the following scenario:
(it’s the blog thing method)

{exp:weblog:entries weblog="rc_standard" limit="1" disable="categories|member_data|pagination|trackbacks" rdf="off"}

    {exp:lg_replace:haystack needles="{matrix_media backspace="1"}media_{row_count}|{/matrix_media}"}

        {matrix_text}
                <div class="container_3 format">
                    <article class="grid_2">
                        {exp:textile}{text_left}{/exp:textile}
                    </article>        
                
                    <aside class="grid_1">
                        {text_right}
                    </aside>
                </div>
        {/matrix_text}
            
        {matrix_media}
            {exp:lg_replace:replacement needle="media_{row_count}"}
                {if "{media_opt}" == "full"}
                    {exp:imgsizer:size src="{media_url}" width="800"}{sized}{/exp:imgsizer:size}
                {/if}
                {if "{media_opt}" == "two_third"}
                    {exp:imgsizer:size src="{media_url}" width="530"}{sized}{/exp:imgsizer:size}
                {/if}
            {/exp:lg_replace:replacement}
        {/matrix_media}
        
    {/exp:lg_replace:haystack}

{/exp:weblog:entries}

it’s all working fine, until I put in {exp:textile}
it’s working fine with EE typography plugin. it works with Legacy typography, but something prevents textile and LG replace to work together.
I am pretty shure that my setup works. I’ve tested it under several circumstances.

might there even be another, “unofficial” textile plugin?

I would really appreciate your help. since it seems like a textile plugin bug.

cheers
stefan

the same thing will work with {exp:markdown} instead of {exp:textile}.

I wish I knew what causes lg replace from not to work if using textile?

Hi stefan, as we can’t support these 3rd-party add-ons ourselves, the best course of action is to talk to the authors.

Hi stefan, as we can’t support these 3rd-party add-ons ourselves, the best course of action is to talk to the authors.

isn’t {exp:textile} a first party plugin? with professional support?

there must be a reason why {exp:textile} is not working with LG replace…
all other typo plugins, first or second party, work fine with LG replace.
so I guess it’s a textile issue?

what’s your point of view in this?

cheers
stefan

btw: I was talking to leevi about this, but he cannot explain himself… that’s why I’m on this forum!

The two might be using the same hook and overriding each other. Is textile working properly by itself?

The two might be using the same hook and overriding each other. Is textile working properly by itself?

yes, textile is working well on it’s own…
how can I check what hooks they use?
I’m not good in php, could you give me a hint?

stefan

Hi Stefan,

What we can’t do I’m afraid is provide support for the integration of 1st party addons with 3rd party ones. If Textile is working as described then you will have to ask the author of the 3rd party addon to investigate this.

Cheers

Greg

Hi Stefan,

What we can’t do I’m afraid is provide support for the integration of 1st party addons with 3rd party ones. If Textile is working as described then you will have to ask the author of the 3rd party addon to investigate this.

Cheers

Greg

wow, this really sucks…
I already investigated the 3rd party addon developper and he sent me to you guys…

Is this the new forums policy??
I know I haven’t been on the forums for a long time. I can remember support staff being helpful, at least trying to help, and not just saying: NO…

I mean you haven’t even given me a hint!! there’s 2 plugins in the variable… now isn’t there?

this is no good for me…

Stefan,

Is this the new forums policy??
I know I haven’t been on the forums for a long time. I can remember support staff being helpful, at least trying to help, and not just saying: NO…

Through a series of responses you confirmed that EE and the Textile plugin work on their own just fine. The Technical Support forums are for support issues regarding EE and its first party add-ons. We unfortunately do not and have never supported third party add-ons.

I mean you haven’t even given me a hint!! there’s 2 plugins in the variable… now isn’t there?

I am not familiar with Leevi’s plugin so I can’t even begin to show you where it might be breaking. What happens when you use both together? Do you get an error? Is it empty?

You are also using Brandon’s Matrix. Are you sure it is not this which is breaking our plugin for you?

The only suggestion I can make right now is that you could try adding the parse parameter to the textile plugin.

{exp:textile parse="inward"}{text_left}{/exp:textile}

If this doesn’t work you will need to reduce your template to be sure you have the correct add-on which is doing the breaking and then as Greg says contact the author again regarding this.

If you require further clarification or have any other questions regarding our policy please feel free to email .(JavaScript must be enabled to view this email address)

Stefan,

Is this the new forums policy??
I know I haven’t been on the forums for a long time. I can remember support staff being helpful, at least trying to help, and not just saying: NO…

Through a series of responses you confirmed that EE and the Textile plugin work on their own just fine. The Technical Support forums are for support issues regarding EE and its first party add-ons. We unfortunately do not and have never supported third party add-ons.

I mean you haven’t even given me a hint!! there’s 2 plugins in the variable… now isn’t there?

I am not familiar with Leevi’s plugin so I can’t even begin to show you where it might be breaking. What happens when you use both together? Do you get an error? Is it empty?

You are also using Brandon’s Matrix. Are you sure it is not this which is breaking our plugin for you?

The only suggestion I can make right now is that you could try adding the parse parameter to the textile plugin.

{exp:textile parse="inward"}{text_left}{/exp:textile}

If this doesn’t work you will need to reduce your template to be sure you have the correct add-on which is doing the breaking and then as Greg says contact the author again regarding this.

If you require further clarification or have any other questions regarding our policy please feel free to email .(JavaScript must be enabled to view this email address)

hi there,

so I did some further testing,

without matrix: same result
with parse=“inward”: same result… in fact, textile is already the first plugin that get’s rendered… I tried parse=“inward” on lg replace aswell… same result…

BTW:
if you tell me to contact the authors, it’s exactely what I am doing…
I am contacting leevi and you guys… and you just shoudn’t say… go contact only the other party (you are also involved)... what if all developpers were as difficult? it’s a plugin made by rick ellis! and he hired you to support his stuff? should I contact him directely? or what are you trying to tell me??

take a look at the screenshot…

and thank you john for trying to help!
this is what I normally expect from the forums!

stefan

Hi, Stefan -

We have done in this thread what we are able to do - that is confirm that the first-party add-ons are working.  You did that early on.  We can not support third-party add-ons.

Instead of playing with parse-order, have you considered setting the custom field to type “Textile”?

I also edited your post for language -these are professional forums, please keep it professional.  That means no cussing.

Thank you.

Just had this same issue, quite easy to fix.

Open up pi.textile.php and add these lines in the Textile function around line 178 for EE1 and line 184 for EE2:

// reset nsm transplant/lg replace tags when using extension and plugin
      $text = str_replace(array('{', '}'), array('{', '}'), $text);

above

$this->return_data = $text;

And that will make textile play nice with LG Replace and NSM Transplant.

Thanks for the assist, Dave. Closing older thread. Don’t hesitate to post again as needed.