XOOPS 
Forum
Forum Index General Forums Community Support Modules Support Themes Support Development International Support Module Hack Reviews Theme Designer Talk
  1. Board index / 
  2. XOOPS Modules Support forums / 
  3. Module troubleshooting 
  4.  / Xoops 2.2.4: Profile and WordPress conflict!
Register
1
draj
Xoops 2.2.4: Profile and WordPress conflict!

  • 2006/1/29 9:30

  • draj

  • Quite a regular

  • Posts: 271

  • Since: 2005/6/23


Hallo!

Did anyone have a similar Problem? Hier ist what I have:

I upgraded XOOPS to 2.2.4. I activated WordPress sometime later.

Called the function from Admin: Email users. Clicking on Username in the Listing it gives following error:

Fatal error: Allowed memory size of 12582912 bytes exhausted (tried to allocate 3840 bytes) in

modules/wordpress/wp-includes/template-functions-general.php on line 582

Any ideas?
2
phppp
Re: Xoops 2.2.4: Profile and WordPress conflict!

  • 2006/1/30 14:00

  • phppp

  • XOOPS Contributor

  • Posts: 2857

  • Since: 2004/1/25


It is not a WordPress module problem but something wrong (Can anyone confirm this?) in Profile "Email users" that causes the memory error, and it "HAPPENS" to display on the WP page.
3
draj
Re: Xoops 2.2.4: Profile and WordPress conflict!

  • 2006/1/30 14:07

  • draj

  • Quite a regular

  • Posts: 271

  • Since: 2005/6/23


Hi!

Thanks for the reply.

If the module is de-activated, this error is (obviously) not there and profiles module works fine like before! I can reproduce as many times as I want by de-activating it!
4
draj
Re: Xoops 2.2.4: Profile and WordPress conflict!

  • 2006/1/30 14:23

  • draj

  • Quite a regular

  • Posts: 271

  • Since: 2005/6/23


Hallo!

The error is repeated even if I click on the index of profiles module. I forgot to mention this. There is a clear conflict between the two!

Mind you, I am using 2.2.4!
5
phppp
Re: Xoops 2.2.4: Profile and WordPress conflict!

  • 2006/1/30 14:23

  • phppp

  • XOOPS Contributor

  • Posts: 2857

  • Since: 2004/1/25


Will check it
6
phppp
Re: Xoops 2.2.4: Profile and WordPress conflict!

  • 2006/1/30 14:26

  • phppp

  • XOOPS Contributor

  • Posts: 2857

  • Since: 2004/1/25


BTW, could anyone else confirm this?

I am not able to reproduce it with on local machine or on my sites.
7
msdana
Re: Xoops 2.2.4: Profile and WordPress conflict!

  • 2006/1/30 14:42

  • msdana

  • Just can't stay away

  • Posts: 817

  • Since: 2005/12/11


I don't get any errors when I perform these actions.

However, I posted my prob on the XPress blog.
If God is watching us, the least we can do is be entertaining.
Graphic Worx : Xoops Themes
8
draj
Re: Xoops 2.2.4: Profile and WordPress conflict!

  • 2006/1/30 18:32

  • draj

  • Quite a regular

  • Posts: 271

  • Since: 2005/6/23


Hallo phppp!

Well, then it a problem on my machine and its worth taking a step forward. I am easily able to reproduce the error. I tried all the debug possibilities and would like to post it here. The profile module immediately stops working when WordPress activated. If you need more information, let me know....Many of the debug I have erased, like server info, etc...
le="color: #000000"><?php --------------------------------------------- WordPress Configuration PHP Version::4.3.7 MySQL Version::4.0.18-standard-log XOOPS Version::XOOPS 2.2.4 Wordpress Version::2.00 safemode:ON register_globals:ON magic_quotes_gpc:ON XML extension:ON MB extension:ON WordPress Stats Category count:4 Blog article count:3 Author count:1 -------------- Php Debug on--------------------------- Fatal error: Allowed memory size of 12582912 bytes exhausted (tried to allocate 28 bytes) in modules/wordpress/wp-includes/template-functions-links.php on line 44 Notice [PHP]: Undefined index: id in file modules/content/blocks/ct_navigation.php line 57 Notice [PHP]: Undefined index: id in file modules/content/blocks/ct_navigation.php line 78 Notice [PHP]: Undefined variable: last_post_icon in file modules/newbb/blocks/newbb_block.php line 142 Fatal error: Allowed memory size of 12582912 bytes exhausted (tried to allocate 3840 bytes) in modules/wordpress/wp-includes/template-functions-general.php on line 681 Fatal error: Allowed memory size of 12582912 bytes exhausted (tried to allocate 11520 bytes) in modules/wordpress/wp-includes/classes.php on line 1460 Warning [PHP]: Invalid argument supplied for foreach() in file modules/isearch/class/blacklist.php line 95 Notice [PHP]: Undefined variable: qa in file modules/magazine/xoops_version.php line 509 Notice [PHP]: Undefined variable: qd in file modules/magazine/xoops_version.php line 510 Notice [PHP]: Undefined variable: qa in file modules/magazine/xoops_version.php line 519 Notice [PHP]: Undefined variable: qd in file modules/magazine/xoops_version.php line 520 Notice [PHP]: Undefined variable: qa in file modules/magazine/xoops_version.php line 521 Notice [PHP]: Undefined variable: qd in file modules/magazine/xoops_version.php line 522 Notice [PHP]: Undefined variable: qa in file modules/magazine/xoops_version.php line 523 Notice [PHP]: Undefined variable: qd in file modules/magazine/xoops_version.php line 524 Notice [PHP]: Undefined variable: qa in file modules/magazine/xoops_version.php line 525 Notice [PHP]: Undefined variable: qd in file modules/magazine/xoops_version.php line 526 -------Mysql/Block Debug on-------------- Once it showed a blank pages. Thereafter tried many times and showed different info.... Fatal error: Allowed memory size of 12582912 bytes exhausted (tried to allocate 11520 bytes) in modules/wordpress/wp-includes/classes.php on line 1460 Fatal error: Allowed memory size of 12582912 bytes exhausted (tried to allocate 11520 bytes) in modules/wordpress/wp-includes/template-functions-links.php on line 102 Fatal error: Allowed memory size of 12582912 bytes exhausted (tried to allocate 3840 bytes) in modules/wordpress/wp-includes/template-functions-general.php on line 681 Fatal error: Allowed memory size of 12582912 bytes exhausted (tried to allocate 11520 bytes) in modules/wordpress/wp-includes/template-functions-links.php on line 56 Fatal error: Allowed memory size of 12582912 bytes exhausted (tried to allocate 3840 bytes) in modules/wordpress/wp-includes/template-functions-general.php on line 689 Fatal error: Allowed memory size of 12582912 bytes exhausted (tried to allocate 11520 bytes) in modules/wordpress/wp-includes/template-functions-general.php on line 620 Fatal error: Allowed memory size of 12582912 bytes exhausted (tried to allocate 46080 bytes) in modules/wordpress/wp-includes/template-functions-general.php on line 440 --------Smarty Debug Debug on------------- Smarty Debug Console included templates & config files (load time in seconds): themes/mytheme/themeadmin.html (0.08919) (total) default/navigation/theme_adminnav.html (0.01015) assigned template variables: {$SCRIPT_NAME} /modules/system/admin.php {$adminmenu} Array (38) ................................ 10 => Array (4) name => Extended Profile dirname => profile version => 10 links => Array (4) 4 => Array (3) title => User link => http://www.website.de/modules... target => empty 2 => Array (3) title => Kategorien link => http://www.website.de/modules... target => empty 3 => Array (3) title => Felder link => http://www.domain.com/modules... target => empty 5 => Array (3) title => Permissions link => http://www.domain.com/modules... target => empty .............................. 40 => Array (4) name => WordPress dirname => wordpress version => 200 links => Array (4) 0 => Array (3) title => Index link => http://www.domain.com/modules... target => empty 1 => Array (3) title => Permission link => http://www.domain.com/modules... target => empty 2 => Array (3) title => Block link => http://www.domain.com/modules... target => empty 3 => Array (3) title => Option link => http://www.domain.com/modules... target => empty ........................ {$adminmenucount} 39 {$systemmenu} Array (4) name => System dirname => system version => 213 links => Array (13) 1 => Array (3) title => Gruppen link => http://www.domain.com/modules... target => empty 3 => Array (4) title => Preferences link => http://www.domain.com/modules... target => empty sublinks => Array (33) 0 => Array (2) name => System cats => Array (6) 0 => Array (2) 5 => Array (2) name => Extended Profile cats => Array (2) 0 => Array (2) link => http://www.domain.com/modules... title => System Configuration 1 => Array (2) link => http://www.domain.com/modules... title => User Preferences 31 => Array (2) name => WordPress cats => Array (1) 0 => Array (2) link => http://www.domain.com/modules... title => ModulPreferences ....................... {$xoops_banner} {$xoops_charset} ISO-8859-1 {$xoops_contents} nnnn<div style="float: left; width: 4... {$xoops_dirname} system {$xoops_footer} empty {$xoops_imageurl} http://www.domain.com/themes/mytheme/ {$xoops_isadmin} 1 {$xoops_isuser} 1 {$xoops_meta_author} http://www.domain.com {$xoops_meta_copyright} Copyright © 2001-2006 {$xoops_meta_description} empty {$xoops_rootpath} {$xoops_sitename} domain.com {$xoops_theme} mytheme {$xoops_themecss} http://www.domain.com/themes/... {$xoops_uname} {$xoops_upload_url} http://www.domain.com/uploads {$xoops_url} http://www.domain.com {$xoops_version} XOOPS 2.2.4 assigned config file variables (outer template scope): {#files#} Array (0) {#vars#} Array (0) -------------- Debug off---------------------------
9
draj
Re: Xoops 2.2.4: Profile and WordPress conflict!

  • 2006/1/30 18:35

  • draj

  • Quite a regular

  • Posts: 271

  • Since: 2005/6/23


Well, thats funny!

While pasting the code below without the code tags, the forum software eats the rest. Try it out and as a CBB expert, you may want to know, when you are planning to blow your mind with my problem, anyway...Just copy the code without the [ ..code..] tags and insert into this forum text window and click on preview!!!

le="color: #000000"><?php {$xoops_js} //--></script><script type="text/java... {$xoops_meta_author} www.domain.com {$xoops_meta_copyright} Copyright © 2001-2006 {$xoops_meta_description} empty {$xoops_rootpath} {$xoops_sitename} domain.com {$xoops_theme} mytheme {$xoops_themecss} http://www.domain.com/themes/... {$xoops_uname} {$xoops_upload_url} http://www.domain.com/uploads {$xoops_url} http://www.domain.com {$xoops_version} XOOPS 2.2.4 assigned config file variables (outer template scope): {#files#} Array (0) {#vars#} Array (0) -------------- Debug off---------------------------
10
adium
Re: Xoops 2.2.4: Profile and WordPress conflict!

  • 2006/1/30 23:10

  • adium

  • Just popping in

  • Posts: 99

  • Since: 2005/1/18


I am having the same problem except its not with my profile it is with my WF-Channel and WF-Sections modules. Everything else on my site works fine except these WF modules.

I get the error:

Fatal error: Cannot redeclare get_page() (previously declared in /home/adium/public_html/modules/wfchannel/index.php:98) in /home/adium/public_html/modules/wordpress/wp-includes/functions.php on line 667

Direct link for the module with the error is http://www.razornylon.com/modules/wfchannel/

Anyone know how I can get these two to play well with each other? I didn't think they were related.
(1) 2 »

Login

Register now!  |  Lost Password?

Search

Advanced Search

Recent Posts

Donat-O-Meter

Stats
Goal: $15.00
Due Date: Jul 31
Gross Amount: $0.00
Net Balance: $0.00
Left to go: $15.00
Make donations with PayPal!

Latest GitHub Commits