<?xml version="1.0" encoding="utf-8" ?><rss version="2.0" xml:base="https://www.webmaster-forums.net/crss/node/1034979" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title></title>
    <link>https://www.webmaster-forums.net/crss/node/1034979</link>
    <description></description>
    <language>en</language>
          <item>
    <title></title>
    <link>https://www.webmaster-forums.net/serverside-scripting/please-translate-tech-supports-comments#comment-1203011</link>
    <description> &lt;p&gt;Renegade is right, // for single line (or #) and /* */ for multi-line.&lt;/p&gt;
 </description>
     <pubDate>Mon, 26 Jun 2006 22:50:24 +0000</pubDate>
 <dc:creator>CptAwesome</dc:creator>
 <guid isPermaLink="false">comment 1203011 at https://www.webmaster-forums.net</guid>
  </item>
  <item>
    <title></title>
    <link>https://www.webmaster-forums.net/serverside-scripting/please-translate-tech-supports-comments#comment-1203006</link>
    <description> &lt;blockquote class=&quot;bb-quote-body&quot;&gt;&lt;p&gt;&lt;strong&gt;mairving wrote:&lt;/strong&gt; 1. You shouldn&#039;t need to have the php but it is always a good idea to have it anyway.&lt;br /&gt;
2. Those are for HTML comments not php. PHP comments are either \\ or \* *\&lt;/p&gt;&lt;/blockquote&gt;
&lt;p&gt;I thought it was //  and /* */ to comment in PHP &lt;img src=&quot;https://www.webmaster-forums.net/misc/smileys/plain.png&quot; title=&quot;Plain&quot; alt=&quot;Plain&quot; class=&quot;smiley-content&quot; /&gt;&lt;/p&gt;
 </description>
     <pubDate>Mon, 26 Jun 2006 22:02:51 +0000</pubDate>
 <dc:creator>Renegade</dc:creator>
 <guid isPermaLink="false">comment 1203006 at https://www.webmaster-forums.net</guid>
  </item>
  <item>
    <title></title>
    <link>https://www.webmaster-forums.net/serverside-scripting/please-translate-tech-supports-comments#comment-1202999</link>
    <description> &lt;p&gt;do an echo of $_SERVER[&#039;DOCUMENT_ROOT&#039;]; to make sure the path has not changed. If it has, you can always do&lt;br /&gt;
&lt;div class=&quot;codeblock&quot;&gt;&lt;code&gt;$inc_path = $_SERVER[&amp;#039;DOCUMENT_ROOT&amp;#039;].&amp;#039;/includes/&amp;#039;;&lt;br /&gt;include($inc_path.&amp;#039;header.php&amp;#039;);&lt;/code&gt;&lt;/div&gt;&#039;&lt;/p&gt;
&lt;p&gt;the  that are in the include, since the comment will ignore other  it finds. Thus:&lt;/p&gt;
&lt;p&gt;&amp;lt;--&lt;br /&gt;
something&lt;/p&gt;
&lt;p&gt;another thing&lt;br /&gt;
--&amp;gt;&lt;/p&gt;
&lt;p&gt;will hide &#039;something&#039; and &#039;something else&#039;, but not &#039;another thing&#039;&lt;/p&gt;
 </description>
     <pubDate>Mon, 26 Jun 2006 18:44:34 +0000</pubDate>
 <dc:creator>CptAwesome</dc:creator>
 <guid isPermaLink="false">comment 1202999 at https://www.webmaster-forums.net</guid>
  </item>
  <item>
    <title></title>
    <link>https://www.webmaster-forums.net/serverside-scripting/please-translate-tech-supports-comments#comment-1202997</link>
    <description> &lt;p&gt;The issue probably had something to do with an update to PHP. I had some issues recently after an update with the DOCUMENT_ROOT directory not being defined. Another issue was caused by some register globals issues. It seems like there was an issue with includes not working properly as well.&lt;/p&gt;
&lt;p&gt;Did you try it with the &amp;lt;?php tag? I doubt if it will make a difference though.&lt;/p&gt;
 </description>
     <pubDate>Mon, 26 Jun 2006 18:09:17 +0000</pubDate>
 <dc:creator>mairving</dc:creator>
 <guid isPermaLink="false">comment 1202997 at https://www.webmaster-forums.net</guid>
  </item>
  <item>
    <title></title>
    <link>https://www.webmaster-forums.net/serverside-scripting/please-translate-tech-supports-comments#comment-1202988</link>
    <description> &lt;p&gt;There are actually two issues.  Before I commented it out, the include to a scipt was working fine but the script being called is what failed (even though it had worked fine for the past year up until recently).   (The script is from &lt;a href=&quot;http://www.cutephp.com&quot; class=&quot;bb-url&quot;&gt;cutephp.com&lt;/a&gt;)  I do get an error message but it&#039;s not from the include, but from the script being called.  If it matters the error is &lt;code&gt;Parse error: syntax error, unexpected $end in /home/pstvalu/public_html/news/inc/functions.inc.php on line 232&lt;/code&gt;&#039;  But the admin page (totally different page) also stopped working the exact same day.  It just sounds ridicuouls to me that a script that&#039;s been working flawlessly for over a year would suddenly fail to function in multiple different pages, on multiple sites, all at once.&lt;/p&gt;
&lt;p&gt;Now about the commenting, I know that &#039;s and class tags to simplify my post.  Since there was actually html around that include call and I wanted to hide the all of it, shouldn&#039;t the&lt;/p&gt;
 </description>
     <pubDate>Mon, 26 Jun 2006 17:08:03 +0000</pubDate>
 <dc:creator>fifeclub</dc:creator>
 <guid isPermaLink="false">comment 1202988 at https://www.webmaster-forums.net</guid>
  </item>
  <item>
    <title></title>
    <link>https://www.webmaster-forums.net/serverside-scripting/please-translate-tech-supports-comments#comment-1202983</link>
    <description> &lt;p&gt;What&#039;s the error you are getting?  Is it something about basedir restriction?&lt;/p&gt;
 </description>
     <pubDate>Mon, 26 Jun 2006 16:35:26 +0000</pubDate>
 <dc:creator>Shirthead</dc:creator>
 <guid isPermaLink="false">comment 1202983 at https://www.webmaster-forums.net</guid>
  </item>
  <item>
    <title></title>
    <link>https://www.webmaster-forums.net/serverside-scripting/please-translate-tech-supports-comments#comment-1202981</link>
    <description> &lt;p&gt;1. You shouldn&#039;t need to have the php but it is always a good idea to have it anyway.&lt;br /&gt;
2. Those are for HTML comments not php. PHP comments are either \\ or \* *\&lt;/p&gt;
 </description>
     <pubDate>Mon, 26 Jun 2006 16:17:55 +0000</pubDate>
 <dc:creator>mairving</dc:creator>
 <guid isPermaLink="false">comment 1202981 at https://www.webmaster-forums.net</guid>
  </item>
  </channel>
</rss>
