We use cookies to improve your experience. No personal information is gathered and we don't serve ads. Cookies Policy.

ExpressionEngine Logo ExpressionEngine
Features Pricing Support Find A Developer
Partners Upgrades
Blog Add-Ons Learn
Docs Forums University
Log In or Sign Up
Log In Sign Up
ExpressionEngine Logo
Features Pro new Support Find A Developer
Partners Upgrades
Blog Add-Ons Learn
Docs Forums University Blog
  • Home
  • Forums

Wygwam, Structure and LG Add Sitename not playing nice

Development and Programming

Charcoal Marketing's avatar
Charcoal Marketing
112 posts
16 years ago
Charcoal Marketing's avatar Charcoal Marketing

I just bought Brandon Kelly’s Wygwam and tried it out. It’s awesome! Finally the answer to my EE WYSIWYG needs!

Thing is, it doesn’t seem to work with some other common third-party extensions, like LG Add Sitename (v.1.2.0) or Structure Extension (v.1.3.1). I had noticed in the past that Playa didn’t work with the LG Add Sitename extension either. Right now when all are enabled and I try to publish a new page, the page just goes blank. I don’t think it’s a PHP memory limit.

Has anyone else been able to use all of these extensions together? Is there some code somewhere that you need to change to get them to play nice?

Any help would be appreciated

       
aimelise's avatar
aimelise
31 posts
16 years ago
aimelise's avatar aimelise

I also have Wygwam and Structure installed here: http://gsis.amystoddard.com. The site isn’t very far developed, but Wygwam is working nicely.

Is your “system > extensions > fieldtypes > wygwam” directory is set to 755?

       
Charcoal Marketing's avatar
Charcoal Marketing
112 posts
16 years ago
Charcoal Marketing's avatar Charcoal Marketing

I just learned it was my PHP memory – needed to be set to 16M instead of 8.

       
moonbeetle's avatar
moonbeetle
81 posts
16 years ago
moonbeetle's avatar moonbeetle

I had exactly the same problem when using latest versions of: LG Add Sitename + FieldFrame + Structure Turning extensions on/off lead to misleading assumptions but after a while I also found out it was the PHP memory limit that needed to be increased.

I recommend checking the PHP error log (if that would have been my first step I would have saved myself quite some debugging time). Nevertheless, monitoring extension that consume a lot of memory is something to watch out for.

       

Reply

Sign In To Reply

ExpressionEngine Home Features Pro Contact Version Support
Learn Docs University Forums
Resources Support Add-Ons Partners Blog
Privacy Terms Trademark Use License

Packet Tide owns and develops ExpressionEngine. © Packet Tide, All Rights Reserved.