Ace_Armstrong wrote:
Actually, I had alrady found those when I posted and changed them. It did not affect the output.

Ace_Armstrong wrote:
I have no idea how to do any of that. I'm a design guy, not a programmer.

peterr wrote:
Quote:

Ace_Armstrong wrote:
I can't find any reference to "640" or "630" anywhere in the code. I have gone through literally every file in the module and every file in the "common" directory.

Have a look at the db, the table name is "xoops_tplsource", and there are several occurances of '640' there. If I look in the corresponding table called "xoops_tplfile", the template files that have those values (in the db) are:

* pical_print.html
* pical_event_list.html

Sometimes the template row in the db is not the same as the template sitting in a path on the server.

peterr wrote:
1. I downloaded Gubed PHP Debugger, which certainly seems to be a good tool, set breakpoints, and step through code, but of course, the PHP code needs to be on a 'local' server, an IP on your LAN somewhere.

2. You could try using
PHPXref, which is a very good cross-ref utility, it is open source, and to see a demo of how it works, there is a site that has all the osCommerce source code, as a demo for PHPXref, see http://www.oscdox.com/crossx/nav.html?index.html

I have loaded that locally in the past, takes up a bit of space, because it creates a load of html pages, but it is a very handy tool for finding out where functions and variables are used.

3. The only suggestion I can make to find out _where_ to change the code, is to walk down a path I _may_ take. With the use of Gubed, I'm chewing on loading something like 'phpdev', which is a bundled Apache, PHP, Mysql,etc, and run it on an old Win95b box I have, then I start up the web server locally, run XOOPS, and then look at using Gubed to debug piCal.