<?xml version="1.0" encoding="UTF-8"?>    <rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
      <channel>
        <title></title>
        <link>https://interactivetools.com/forum/forum-search.php?k=user%3ATrevmac</link>
        <description></description>
        <pubDate>Mon, 08 Jun 2026 08:00:57 -0700</pubDate>
        <language>en-us</language>
        <atom:link href="https://interactivetools.com/forum/forum-search.php?k=user%3ATrevmac&amp;rss=1" rel="self" type="application/rss+xml" />

                <item>
          <title>News Manager issue</title>
          <link>https://interactivetools.com/forum/forum-posts.php?postNum=2204867#post2204867</link>
          <description><![CDATA[Hi,<br /><br />I have NM installed for a client that has been working for a few years now. Their isp migrated their website to a new server. When my client tries to login to http://www.theirsite.co.uk/nm/exec/admin.cgi they get a 404 error. I am using Dreamweaver and when I look at the permissions set for admin.cgi they read as 644. I asked the hosts to change the permissions to 755 which they assure me they have (I still see them as 644) but there is still a 404 error. They say that I have a path problem:<br /><br />From isp:<br /><br />found this via google seems to be the same error - they also had the same path error<br /><br />&quot;To allow your customers to install your CGI wherever they want, I suggest that you fix your CGI to use the Server Variable (or CGI environment variable) SCRIPT_NAME to generate the correct URI for ACTION. SCRIPT_NAME resolves back to the URL that invoked the CGI, wherever the user installed it. So, for a first run URL of http://mysite.com/cgi-bin/prog.cgi , SCRIPT_NAME returns /cgi-bin/prog.cgi... which should correctly resolve as ACTION for your subsequent PostBack.<br /><br />If you just use &quot;prog.cgi&quot; as ACTION, you are assuming that the BROWSER resolves /cgi-bin as the base directory of the request and makes the PostBack to /cgi-bin/prog.cgi. If the browser does not resolve /cgi-bin as the base directory, the PostBack likely results in a 404. You can verify this with the server log file corresponding to the failed PostBack that results in a 404.&quot;<br /><br />If this is indeed a path problem how do I make the relevant change to NM?<br /><br />My client is getting quite agitated so if you could please point me in the correct direction I would really appreciate it.<br /><br />Thanks in advance<br />]]></description>
          <pubDate>Mon, 14 Jun 2010 07:17:42 -0700</pubDate>
          <guid isPermaLink="true">forum-posts.php?postNum=2204867#post2204867</guid>
        </item>
                <item>
          <title>Couple of questions for you</title>
          <link>https://interactivetools.com/forum/forum-posts.php?postNum=2191163#post2191163</link>
          <description><![CDATA[Hi all,<br /><br />I am putting together a proposal for a client to produce a disability charity website. It needs to be fully WIA compliant and content managed by the client. I am looking for a CMS system that can be added to my design and outputs WIA fully compliant code.<br /><br />Question 1:<br />How good is CMS builder at outputting code that will be WIA compliant, at least to AA standard and hopefully AAA.<br /><br />Question 2:<br />I may have missed something in the information provided but how would the client actually make the changes to the content. Is it carried out in a similar way to say the updating in &quot;Listings Manager&quot; where the client logs in through a browser and uses forms to enter the info? <br /><br />I have used a couple of the packages from interactivetools before and found them to be very good and reliable. It would be good to use a CMS system from a company that I am already  familiar with and indeed trust.<br /><br />Looking forward to any replies and thanks in advance.<br /><br />Trev.<br />]]></description>
          <pubDate>Fri, 11 Apr 2008 05:47:20 -0700</pubDate>
          <guid isPermaLink="true">forum-posts.php?postNum=2191163#post2191163</guid>
        </item>
              </channel>
    </rss>
  