Elxis CMS Forum

Extensions => Components => Topic started by: fuzzfree on September 04, 2010, 23:38:36

Title: Problem with Newsletter installation
Post by: fuzzfree on September 04, 2010, 23:38:36
When I try to install the component :

PHP Error [Warning]
URI: index2.php
Path: \includes\adodb\adodb-xmlschema03.inc.php
Line: 1981
fopen(C:/PHPdev/WWW/xxx.com/stores.xxx.com/administrator/components/com_newsletter/schema/nlschema03.xml) [function.fopen]: failed to open stream: No such file or directory

+

Could not copy SEO PRO extension (seopro.com_newsletter.php) to folder includes/seopro/
You must manually copy and paste the file to the includes/seopro/ directory and rename it to com_newsletter.php


Inside the administrator/components/com_newsletter/ the proper folders are missing, but they are one path above with naming:
com_newsletterhtmlfiles
com_newsletterimages
com_newsletterincludes
com_newsletterlanguage
com_newsletterschema








SYSTEM INFO:
PHP Built On:     Windows NT SASA 5.1 build 2600
Database Version:    mysql 5.1.45-community (Version: 5.1.45)
PHP Version:    5.2.8
Web Server:    Apache/2.2.9 (Win32) PHP/5.2.8
Web Server to PHP interface:    apache2handler
Version    Elxis 2009.2 Stable rev2631 [ Electra ] 15-June-2010 22:45 GMT+2
User Agent:    Mozilla/5.0 (Windows; U; Windows NT 5.1; en-GB; rv:1.9.2.8) Gecko/20100722 Firefox/3.6.8 ( .NET CLR 3.5.30729)
Relevant PHP Settings:    
Safe Mode:    OFF
Open basedir:    none
Display Errors:    ON
Short Open Tags:    ON
File Uploads:    ON
Magic Quotes:    OFF
Register Globals:    OFF
Output Buffering:    OFF
Session save path:    C:\PHPdev\WWW\TMP
Session auto start:    0
XML enabled:    Yes
Zlib enabled:    Yes
Disabled Functions:    none
WYSIWYG Editor:    TinyMCE WYSIWYG Editor
Title: Re: Problem with Newsletter installation
Post by: Ivan TrebjeŇ°anin on September 05, 2010, 12:40:05
I remember such problem with some WAMP server, but in next version it was fixed. However, judging on your paths, you have separate installations of PHP/Apache/MYSQL. So, it is PHP or apache version that is causing the issue. Try upgrading them, and see if problem still exist.

EDIT:
This problem was appearing ONLY on window$ machines.