Support Forums - All Posts - XOOPS Web Application System

31

Re: Error When Trying To Change Template Set

2009/5/21 12:46
AlexSolo
Not too shy to talk
Posts: 145
Since: 2006/3/8 1

I reported a similar issue with the xoopscare ( reported elsewhere) module. same kind of smarty eror. Just checked my server install:
XOOPS Version - XOOPS 2.3.3
PHP Version - 5.1.6
MySQL Version - 5.0.27
Server API Version - apache2handler
OS Version - Linux

safe_mode - Off
register_globals - Off
magic_quotes_gpc - On
allow_url_fopen - On
fsockopen - On
allow_call_time_pass_reference - Off
post_max_size - 8M
max_input_time - 60
output_buffering - 4096
max_execution_time - 60
memory_limit - 16M
file_uploads - On
upload_max_filesize - 2M
Loaded PHP extensions Â«

* libxml
* xml
* wddx
* tokenizer
* sysvshm
* sysvsem
* sysvmsg
* standard
* SimpleXML
* sockets
* SPL
* shmop
* session
* Reflection
* pspell
* posix
* mime_magic
* iconv
* hash
* gmp
* gettext
* ftp
* exif
* date
* curl
* ctype
* calendar
* bz2
* zlib
* pcre
* openssl
* apache2handler
* gd
* imap
* ldap
* mbstring
* mcrypt
* mhash
* mysqli
* mysql
* odbc
* PDO
* pdo_mysql
* PDO_ODBC
* pdo_sqlite
* Zend Optimizer

As you can see I have a newer install of php than recommended by xoops. Is this my problem?

32

Re: Serious Problem with Xoops care module with 2.3.3

2009/5/21 12:35
AlexSolo
Not too shy to talk
Posts: 145
Since: 2006/3/8 1

Thought it might be my machine. Needs some update somewhere. This is what I have:
XOOPS Version - XOOPS 2.3.3
PHP Version - 5.1.6
MySQL Version - 5.0.27
Server API Version - apache2handler
OS Version - Linux

safe_mode - Off
register_globals - Off
magic_quotes_gpc - On
allow_url_fopen - On
fsockopen - On
allow_call_time_pass_reference - Off
post_max_size - 8M
max_input_time - 60
output_buffering - 4096
max_execution_time - 60
memory_limit - 16M
file_uploads - On
upload_max_filesize - 2M
Loaded PHP extensions Â«

* libxml
* xml
* wddx
* tokenizer
* sysvshm
* sysvsem
* sysvmsg
* standard
* SimpleXML
* sockets
* SPL
* shmop
* session
* Reflection
* pspell
* posix
* mime_magic
* iconv
* hash
* gmp
* gettext
* ftp
* exif
* date
* curl
* ctype
* calendar
* bz2
* zlib
* pcre
* openssl
* apache2handler
* gd
* imap
* ldap
* mbstring
* mcrypt
* mhash
* mysqli
* mysql
* odbc
* PDO
* pdo_mysql
* PDO_ODBC
* pdo_sqlite
* Zend Optimizer

Am I missing something on the server? My xamp install on my test machine runs flawlessly with this same XOOPS package as installed here.

33

Re: Error When Trying To Change Template Set

2009/5/20 23:52
AlexSolo
Not too shy to talk
Posts: 145
Since: 2006/3/8 1

I don't have extcal even installed and I'm getting these similar errors in other alpplications like news and xoopscare totally destroyed my cloned default templates. Funny thing is my local install, xampp on a Mac works perfectly fine. No major problems to think of. I am emailing my provider to see what PHP I have installed and get an upgrade to 5.0. maybe that is the whole problem!

34

Re: Error When Trying To Change Template Set

2009/5/20 19:53
AlexSolo
Not too shy to talk
Posts: 145
Since: 2006/3/8 1

I just had a similar error after running xoopscare (cache and template_c cleaning) on a cloned template package whereby eliminating my ability to have any web pages using the cloned set. Had to revert to the default set. I now cannot use ANY other set other than the default. YTried using a new default set in preferences, i get a similar smarty error. YOU ARE NOT ALONE!

35

Serious Problem with Xoops care module with 2.3.3

2009/5/20 19:45
AlexSolo
Not too shy to talk
Posts: 145
Since: 2006/3/8 1

This is my third clean install of 2.3.3 and after running xoopscare 1.3 "cache and template_c folders feature (only), I lost all page visibility in my cloned default template package. This is the second time it has occurred. Here is the error:
This page cannot be displayed due to an internal error.

You can provide the following information to the administrators of this site to help them solve the problem:

Error: Smarty error: [in db:mpu_menurelated.block.tpl.html line 79]: syntax error: unclosed tag \{if} (opened line 1). (Smarty_Compiler.class.php, line 326)
Backtrace:
/class/smarty/Smarty.class.php (1092)
/class/smarty/Smarty.class.php (1814)
/class/smarty/Smarty_Compiler.class.php (2242)
/class/smarty/Smarty_Compiler.class.php (326)
/class/smarty/Smarty.class.php (1488)
/class/smarty/Smarty.class.php (1421)
/class/template.php (100)
/class/template.php (181)
/modules/system/admin/preferences/main.php (432)
/modules/system/admin.php (80)

I can no longer use the cloned templates but have reverted to the default installation. I will turn off xoopscare untill i get this resolved for fear of this happening on my default templaes as well. Any answers? Xoopcare is an important module and this problem should be looked into immediately for all.

36

Re: New problem after installing and using xoopscare

2009/5/8 20:32
AlexSolo
Not too shy to talk
Posts: 145
Since: 2006/3/8 1

Anybody with more XOOPS experience than I want to help me with this? this is the most serious of problems.

37

Re: Several problems after install on server.

2009/5/7 17:09
AlexSolo
Not too shy to talk
Posts: 145
Since: 2006/3/8 1

Without knowing which files to choose, a shot in the dark approach could cause more harm than good. I looked at frameworks and I wouldn't know what files effect what modules.
Too risky for me with a limited knowledge of php.

38

Re: Several problems after install on server.

2009/5/6 17:57
AlexSolo
Not too shy to talk
Posts: 145
Since: 2006/3/8 1

I am using the newest install of everything. Whatever came with the package 2.3.3. I added nothing additional except for modules and every module except for the content module came from the links from the recent wiki on"what works with 2.3.3. the only thing I did was change some permissions to make some files or folders more accessible. I made no alterations via ftp to ANY file except the theme file. I am using the fck that came with 2.3.3. Framework is one that came with 2.3.3. Main file is 444 as for the others some directories like cache I changed to 777.

See my newest post about installing xoopscare and what has happened.

aditional info:
News 1.63- koivi works, basic works, tinymce - i get my sites black background behind the input area in the form making it not very user friendly but you can input text and save, just cant see what you are inputting.
fck freezes and I get the above error message.

content module- 2 choices, fck (doesn't work, same error) and htmleditor (standard)- can create but not update any content created.

mastop publishing- has it own insall of tinymce in the module.(works)

these are the only 3 modues installed that use wisiwig.

39

New problem after installing and using xoopscare

2009/5/6 15:18
AlexSolo
Not too shy to talk
Posts: 145
Since: 2006/3/8 1

Installed and used xoopscare to flush template_c and cache folders now I get this:
This page cannot be displayed due to an internal error.

You can provide the following information to the administrators of this site to help them solve the problem:

Error: Smarty error: [in db:mpu_menurelated.block.tpl.html line 79]: syntax error: unclosed tag \{if} (opened line 1). (Smarty_Compiler.class.php, line 326)
Backtrace:
/class/smarty/Smarty.class.php (1092)
/class/smarty/Smarty.class.php (1814)
/class/smarty/Smarty_Compiler.class.php (2242)
/class/smarty/Smarty_Compiler.class.php (326)
/class/smarty/Smarty.class.php (1488)
/class/smarty/Smarty.class.php (1421)
/class/template.php (100)
/class/template.php (181)
/modules/system/admin/preferences/main.php (432)
/modules/system/admin.php (80)

I have had to revert back the the defaut template package my cloned package no longer shows any pages. I tried deleating the cloned templares and creating a new set with a different name and cannot use those either. Help ....I am afraid to use xoopscare on the default installation for fear of loosing the whole thing.

I have not altered any files via ftp, just changed some permissions to 777 to get another problem I have been having with fck to work.

any moderator willing to look at my install and fix what I broke?

40

Re: Several problems after install on server.

2009/5/6 14:01
AlexSolo
Not too shy to talk
Posts: 145
Since: 2006/3/8 1

Seems to be partly a permission thing and corrected it on cache but now I am getting this:

Error loading "http://name of site.com/class/xoopseditor/fckeditor/fckeditor/fckstyles.xml" (HTTP Status: 500).

Do you want to see the server response dump?

How to fix this? tried changing permissions for this file did no good.

Stats
Goal:	$100.00
Due Date:	Apr 30
Gross Amount:	$0.00
Net Balance:	$0.00
Left to go:	$100.00

Forum Index

Re: Error When Trying To Change Template Set

Re: Serious Problem with Xoops care module with 2.3.3

Re: Error When Trying To Change Template Set

Re: Error When Trying To Change Template Set

Serious Problem with Xoops care module with 2.3.3

Re: New problem after installing and using xoopscare

Re: Several problems after install on server.

Re: Several problems after install on server.

New problem after installing and using xoopscare

Re: Several problems after install on server.

Login

Search

Recent Posts

Re: Rebuilding and Updating a 20 years old Xoops Website from 2.0.18? to 2.5.11

Rebuilding and Updating a 20 years old Xoops Website from 2.0.18? to 2.5.11

Re: NewBB v 5.1.0 b 6

Re: NewBB v 5.1.0 b 6

NewBB v 5.1.0 b 6

Re: XOOPS 2.5.11 search user is not working

Re: oledrion

Re: oledrion

Re: oledrion

Re: oledrion

Who's Online

Donat-O-Meter

Latest GitHub Commits

{{ record.sha.slice(0, 7) }} - {{ record.commit.message | truncate }}