Inserting PHP code block into content article

Quimbly · 2012-10-02 18:10:03

I’m struggling to do something seemingly simple: insert some markup into an article.

Here are the details:
- My user account permission level is publisher
- The site has all three PHP options enabled: Allow PHP in pages, Allow PHP in articles, Allow raw PHP

Inside an article, I’ve tried all of the following:

———————————————————————————————
Attempt #1
———————————————————————————————

<div class=“slideshow_test1”> <img src=”/images/528.jpg” /> <img src=”/images/28.jpg” /> <img src=”/images/26.jpg” />
</div>
<script type=“text/javascript”>$(document).ready(function(){$(“.slideshow_test1”).cycle({ fx: “fade”, speed: 2000 }); }); </script>

———————————————————————————————
Attempt #2
———————————————————————————————

<txp:php>
<div class=“slideshow_test1”> <img src=”/images/528.jpg” /> <img src=”/images/28.jpg” /> <img src=”/images/26.jpg” />
</div>
<script type=“text/javascript”>$(document).ready(function(){$(“.slideshow_test1”).cycle({ fx: “fade”, speed: 2000 }); }); </script>
</txp:php>

———————————————————————————————
Attempt #3
———————————————————————————————

<txp:php>
<?php
<div class=“slideshow_test1”> <img src=”/images/528.jpg” /> <img src=”/images/28.jpg” /> <img src=”/images/26.jpg” />
</div>
<script type=“text/javascript”>$(document).ready(function(){$(“.slideshow_test1”).cycle({ fx: “fade”, speed: 2000 }); }); </script>
?>
</txp:php>

———————————————————————————————
Attempt #4
———————————————————————————————

<txp:php>
<?php
echo ‘
<div class=“slideshow_test1”> <img src=”/images/528.jpg” /> <img src=”/images/28.jpg” /> <img src=”/images/26.jpg” />
</div>
<script type=“text/javascript”>$(document).ready(function(){$(“.slideshow_test1”).cycle({ fx: “fade”, speed: 2000 }); }); </script>’;
?>
</txp:php>

In each case, I get the following error:
Parse error: syntax error, unexpected ‘<’ in ……../textpattern/publish/taghandlers.php(3748) : eval()’d code on line 1

What am I missing??

Quimbly · 2012-10-02 18:53:01

Ok, finally figured it out… Not sure why this info is so hard to find!

This is the code block that eventually worked:

<notextile>
<txp:php>
echo ‘
<div class=“slideshow_test1”> <img src=”/images/528.jpg” /> <img src=”/images/28.jpg” /> <img src=”/images/26.jpg” />
</div>
<script type=“text/javascript”>$(document).ready(function(){$(”.slideshow_test1”).cycle({ fx: “fade”, speed: 2000 }); }); </script>’;
</txp:php>
</notextile>

So, here are my take-away lessons:

When inserting markup or PHP into a TextPattern content article:

1. Don’t include the usual PHP delineations: <?php … ?>

2. Use PHP, not mark-up:

e.g. Use this: echo ‘<div id=“abc”>blah blah blah</div>’; NOT this: <div id=“abc”>blah blah blah</div>

3. Use must surround the code with both the <txp:php> and <notextile> tags:

e.g. <notextile> <txp:php> … code goes here … </txp:php> </notextile>

Cheers.

Last edited by Quimbly (2012-10-02 20:44:57)

els · 2012-10-02 20:13:24

Glad you figured it out!

Quimbly wrote:

Not sure why this info is so hard to find!

Do you think this page is not clear enough? If so, any suggestions for improvements?

Quimbly · 2012-10-02 20:22:53

There are two problems with the link you provided:

1. That page did not turn up when I Googled the subject using these kinds of terms: textpatterm , insert/add PHP into content article.

2. There is no mention of the <notextile> tag on that page, which was a major stumbling block for me. I was basically following the method described on that page, but it didn’t work, and the error message was unhelpful.

Improvements: add a note about the <notextile> tag and maybe add better meta tags on the page for better search engine results.

maruchan · 2012-10-02 20:36:02

That should cover it. I don’t know about meta tags and the wiki, but I added a heading that search engines should pick up.

Quimbly · 2012-10-02 20:41:52

Awesome! That should help others, I hope. Thanks, gang! You rock!

els · 2012-10-02 21:24:09

Nice, Marc, you beat me to it :)

maruchan wrote:

I added a heading that search engines should pick up.

Wouldn’t search engines pick it up if it were somewhere further on the page? I’m afraid you just violated the guidelines… ;)
I think we should ask Destry if we can have something like this.

maruchan · 2012-10-02 23:02:50

I’m sure it’s not going to compete with many other pages on the web, so placing it just about anywhere would be fine with me. :-) Meta tags are alright but does Google use them for ranking purposes anymore? I thought they stopped doing that…

MattD · 2012-10-02 23:48:17

I’m confused because I don’t see what php code you were trying to insert. If you were trying to insert html markup with javascript then this should work.

notextile.. <div class="slideshow_test1"> <img src="/images/528.jpg" /> <img src="/images/28.jpg" /> <img src="/images/26.jpg" />
</div>
<script type="text/javascript">$(document).ready(function(){$(".slideshow_test1").cycle({ fx: "fade", speed: 2000 }); }); </script>

To break out of the notextile you’d just include a blank line and a p..

Last edited by MattD (2012-10-02 23:49:16)

Quimbly · 2012-10-03 03:22:42

Interesting! Ok, that makes sense.

I had no need to use PHP code other than to output the mark-up. I wasn’t aware of the <notextile> tag, so I had been experimenting with the <txp:php> tag. Again, I’m new to TextPattern, and when Googling, I had a hard time finding an answer to my seemingly simple task.

I’ve tested it out, and yes, if you’re just adding mark-up, the PHP tag is not needed. So, in my case, the following code block works just fine:

<notextile> <div class=“slideshow_test1”> <img src=”/images/528.jpg” /> <img src=”/images/28.jpg” /> <img src=”/images/26.jpg” /> </div> <script type=“text/javascript”>$(document).ready(function(){$(”.slideshow_test1”).cycle({ fx: “fade”, speed: 2000 }); }); </script> </notextile>

merz1 · 2012-10-03 14:27:46

Btw: Put your code snippet into a Textpattern ‘form’ and release it into the wild via <txp:output_form form="my_code_snippet" />.

Btw II.: Reusable slideshow form: The mind bending <txp:yield /> inside a form is great for changing content like batches of pictures inside a txp:output_form container.

Last edited by merz1 (2012-10-03 14:28:03)

uli · 2012-10-03 18:36:29

Quimbly, after six years of working with TXP, I’m not yet certain enough in predicting in what cases I need to camouflage code in articles in order to not have it beautified by Textile, you’re not alone ;) With that said, however, taking a stab at your first attempt: I found the code works for me, it is there, on the page. So there might have been another problem at the time you tried.

But whenever I’m in doubt that code might get swallowed/come out unchanged, I use the quickly typed and easy to remember double equal ==<any code here />==. No hassles whether it needs a blank space before or after or no space at all, it even works on a separate line.

Last edited by uli (2012-10-03 18:37:55)

Destry · 2012-10-04 12:04:38

Many interesting facets to this gem, yes.

Wiki page structure: Yes, we probably want to leave the consistent page structure alone or it will turn into tornado soup pretty quickly. I’ll straighten that out.

Wiki page meta: Meta tags won’t do anything to improve ranking of that page. The problem is the page is titled “PHP” (and that’s not going to change because it’s consistent with tag page titling). How many things online are competing with those three letters? Yeah. It’s like expecting “CMS” alone to race Textpattern to the top. Page section headers are the key (and keywords in body copy), and it shouldn’t matter where on the page. (An h2 is an h2 is an h2, etc. down the line.)

Markup, markdown, mark-around help: With regard to the markup mystery, I’d say we do have a gap (or few) in communicating certain bits of knowledge about Textile (or whatever) when the rare situation come up.

I’ve always been of the mind that the wiki should have a primary side link for “Textile use” or “Markup editing” (less Textile specific so it can cross other filter/syntax territory too), or whatever, where we don’t just show the formatting syntax like you see in the admin-side, but where actual use cases are more specifically demonstrated and easily found than they might otherwise be in tag page examples (still a hit or miss affair there).

Anyone opposed to the idea of doing that? We could start a single page and as examples grow, we organize them and branch out if necessary. Even if it’s just two or three examples, like demonstrated in this thread, it can be worthwhile and make a difference for someone. Here’s another situation that comes to mind that I run into all the time, using straight brackets: e.g., ...an opening clause ending with a ["link"url]--a clause inside em dashes--another clause...). I think I have that right. ;)

Destry · 2012-10-04 12:08:50

Destry wrote:

a primary side link for “Textile use” or “Markup editing” (less Textile specific so it can cross other filter/syntax territory too), or whatever…

Maybe “Formatting”? Or “Content formatting”?

els · 2012-10-04 17:30:11

Destry, because I’m not sure I understand you correctly: do you mean there would be a “formatting” (or whatever you decide to name it) link only on tag pages for which formatting examples exist? Similar to the links to translated tag pages? Or a link to a generic page that contains examples for various tags?

Textpattern CMS

Textpattern CMS support forum

#1 2012-10-02 18:10:03

Inserting PHP code block into content article

#2 2012-10-02 18:53:01

Re: Inserting PHP code block into content article

#3 2012-10-02 20:13:24

Re: Inserting PHP code block into content article

#4 2012-10-02 20:22:53

Re: Inserting PHP code block into content article

#5 2012-10-02 20:36:02

Re: Inserting PHP code block into content article

#6 2012-10-02 20:41:52

Re: Inserting PHP code block into content article

#7 2012-10-02 21:24:09

Re: Inserting PHP code block into content article

#8 2012-10-02 23:02:50

Re: Inserting PHP code block into content article

#9 2012-10-02 23:48:17

Re: Inserting PHP code block into content article

#10 2012-10-03 03:22:42

Re: Inserting PHP code block into content article

#11 2012-10-03 14:27:46

Re: Inserting PHP code block into content article

#12 2012-10-03 18:36:29

Re: Inserting PHP code block into content article

#13 2012-10-04 12:04:38

Re: Inserting PHP code block into content article

#14 2012-10-04 12:08:50

Re: Inserting PHP code block into content article

#15 2012-10-04 17:30:11

Re: Inserting PHP code block into content article

Board footer