Jump to content


christobal

Member Since 24 Aug 2004
Offline Last Active Apr 28 2006 05:20 PM
-----

Topics I've Started

IP resolution problems in email functions

12 November 2004 - 03:19 PM

Have noticed that the newsletter campaign when using 4.7 on windows machine with php and apache generates a e-mail (port 25) procedure using IP 127.0.0.1 instead of using SMTP Server IP address as configured in PHP.INI .
The campaign registers itself as successful but alas nothing is sent to recipients from UDT_mynewsletter table.

Also when using "e-mail this page to a friend". The process successfully sends the e-mail to the requested recipient but alas the link supplied in the mail message is of the format http://localhost.xxx.xxx instead of the the resolution of the server address http://christobal.xxxx.xxx

Any thoughts how this problem be overcome

Mutli-lingual display sites-- could there be a way?

10 October 2004 - 06:23 PM

To the best of my comprehension the menu builder uses the page name to display the menu item. This is fine when using latin based character sets, but only allows a single menu presentation layer.
-------- Food for thought !!
Could an additional field be incorpated into the menu builder which when marked produces an alternative text string ( preferably managed in the page properties object) to be displayed in the menu variable or alternatively used as a new #Tag# i.e. #VMENU1#, #HMENU1# etc. This proposed tag variable would obviously be supported in the template structure.
Such an addition would allow multi-lingual sites ------------------

The alternative text field obiviously stored in the site_pages table would be able to display the value stored regardless of the character set by simply marking the relevant template files with the correct meta content type in the html code for the character set to be displayed .

Improvements previously discussed (a recap)

10 October 2004 - 09:23 AM

Before the release of the 4.7 Betas and in the days of the old forum, there was a lot of discussion on the inclusion of a file-management layout.
To reiterate the discussion as it was.
A number of forum members suggested that there is a need to include a file-management script which allows for the separation or classification of different content types instead of the single file list which is currently in place.

From my delvings into the internals of the file structure used.The files are already caterogised according to type, that is to say: after uploading, the image type files are automatically placed in the root/images folder and the content/script: -csv,inc(renames php files), txt and form files are placed in the root/media folder. The same rule is applied in the page editor script. When choosing the object images, the file dropdown list only includes the content of the root/images folder. The same applies to the custom code object.

The only place in my opinion which requires "a spruce up" is the file manager window which instead of a flatfile presentation should show the files in their seperate catergories

Hope to Help

Handling OS type globals

21 September 2004 - 04:47 AM

The SMT addresses the foliowing machine configurations:

Windows OS ( Assumming IIS ) or
Linux (apache)
When running setup on a Windows machine with Apache the setup registers globals as Linux Machine.
From Code:
########################################################
// Register as global for use elsewhere
if (!session_is_registered("WIN_FULL_PATH")) { session_register("WIN_FULL_PATH"); }
$WIN_FULL_PATH = ""; // For Linux Servers

$filename = "sohoadmin/config/isp.conf.php";

// Let's Look at what global vars are available to us so that we can determine
// if this is a Windows Server, Windows Server w/Sphera or Linux Server

if (eregi("WIN", $WINDIR)) { // Windows Server


$WIN_FULL_PATH = $PATH_TRANSLATED;
$tmp = eregi_replace("/","\\\\", $PHP_SELF);
$WIN_FULL_PATH = eregi_replace("$tmp", "", $WIN_FULL_PATH);

// Set the configuration file location using full path (Win)
$filename = $WIN_FULL_PATH . "\\sohoadmin\\\\config\\\\isp.conf.php";

/} // End Build Win Full Path
#####################################################
This structure leaves the Windows/Apache Machine in a state of confusion:

When structure is remarked as below then the path translation behaves correctly

#####################################################
// Register as global for use elsewhere
//if (!session_is_registered("WIN_FULL_PATH")) { session_register("WIN_FULL_PATH"); }
$WIN_FULL_PATH = ""; // For Linux Servers

$filename = "sohoadmin/config/isp.conf.php";

// Let's Look at what global vars are available to us so that we can determine
// if this is a Windows Server, Windows Server w/Sphera or Linux Server

//if (eregi("WIN", $WINDIR)) { // Windows Server


// $WIN_FULL_PATH = $PATH_TRANSLATED;
// $tmp = eregi_replace("/","\\\\", $PHP_SELF);
// $WIN_FULL_PATH = eregi_replace("$tmp", "", $WIN_FULL_PATH);

// Set the configuration file location using full path (Win)
// $filename = $WIN_FULL_PATH . "\\sohoadmin\\\\config\\\\isp.conf.php";
///
//} // End Build Win Full Path
#################################################
Could we see in future releases a workaround other than remarking code for this now more popular configuration.
TNX! ;)

Autodatestamp

19 September 2004 - 07:20 PM

A tag that seems to have been omitted from the tags list ----- In my humble opion -----
one of the better ones when working with templates

#AUTODATESTAMP# :cool: