Hot answers tagged

5

This isn't really EE specific - you'd load the forum in an iframe like you'd load anything else in an iframe. That said - loading it in an iframe isn't a good idea. If you want to use your global header and footer (embeds/snippets?) in the forum then run your forum through the regular template engine using the {exp:forum} tag. More info about that here: ...


4

I've never fully understood why EllisLabs opted for building a completely separate module for forums when the structure of ExpressionEngine can be used to create fully bespoke forums. You have a channel called forums, pre-defined categories for sections of the forum - so mimicking EE's own forums, you have a parent category of "ExpressionEngine 2" and 2 ...


3

That's the native EE forum template. I suggest using the jQuery Validation plugin http://jqueryvalidation.org/. You can add the code to the forum header template. I don't know the header template name offhand but it should be in the same directory. <form id="registration" action=""> <input id="email" type="email" name="email" required> &...


3

I followed this old EE thread and got a WYSIWYG in place. I modified the forum_themes/scaffold/forum_global/html_footer.html, adding this snippet: <script src="//ajax.googleapis.com/ajax/libs/jquery/2.0.3/jquery.min.js"></script> <script src="/themes/third_party/wygwam/lib/ckeditor/ckeditor.js"></script> <script src="/themes/...


2

You will want to modify your Word Censoring preferences which will replace bad words with hash marks, e.g. ######.


2

Generally, EllisLab requires that each new release of their additional modules (MSM and Forum) be used only with the version of ExpressionEngine that was released at the same time - they don't maintain backwards-compatibility. If you have a valid license for the Forum module, and cannot upgrade from EE 2.3.0, then I'd contact EllisLab directly, provide your ...


2

No, there are not. To style the forum you have to edit the theme files directly. EllisLab's reommendation per the documentation: If you plan to make changes to your theme, we recommend that you make a copy of the themes/forum_themes/default/ directory, name it something else, and make your changes to that one. Instead of doing that, I suggest taking ...


2

Add $config['disable_csrf_protection'] = "y"; to your config file, you need to add the XID to the form in a hidden field to get rid of the error the other way.


1

Checked the documentation and found that the correct code is $temp['answer'] = ee('Security/XSS')->security->xss_clean($val); Ref: https://docs.expressionengine.com/v2/development/guidelines/security.html


1

It depends on your sites primary purpose. Either you have content that is supported by a forum to discuss the content or you have a forum that has some additional content to support the forum. If the later then the forum is more important that the content and the functionality of the forum will be paramount. In that case the EE forum might not be the best ...


1

The "default email format" setting does only one thing, and that is determine the initial state of the "Email Format" dropdown when you go to Tools → Communicate. All other emails generated by EE - be it from the Forum module, or comment notifications, new entry notifications, etc - will be sent as plain text. Currently there is no way to change that ...


1

Just had exactly the same issue. The {if pm_enabled} {/if} conditional was only added in 2.10.0 which is causing the error. https://ellislab.com/expressionengine/user-guide/about/changelog.html#version-2-10-0 Upgrading EE to the latest fixes the issue.


1

I don't have any personal expirience with those add-ons, but there are bridges for Vanilla and vBulletin


1

Ended up paying EllisLab for support only to find out the newest version of Discussion Forum only works with EE v2.8+. They provided the next version down which is working fine.


1

Use the {switch} tag. Separate switches by the | pipe character, they will cycle through. {exp:channel:entries channel="news" limit="10" switch="green|blue|red"} <h2 class="{switch}">{title}</h2> {/exp:channel:entries} Will output <h2 class="green">My title</h2> <h2 class="blue">My title</h2> <h2 class="red">...


1

"You can moderate *who* is allowed to post, but not the posts themselves." http://ellislab.com/forums/viewthread/219793/#1013472 I'm not sure, but maybe you can create a post-only forum (for the "new-member" group) and once approved move the message to the regular forums and assign the user to "regular-members" group.


1

Several years ago, the EllisLab staff posted something about having a replacement for the hilariously outdated forum package that EE ships with. Then EE4 came out.... then EE5 came out.... then EllisLab was acquired.... and we've not heard of it since. I suspect it is dead, and never to see the light of day. :(


1

As Derek stated above, this all depends on the version of the Forum module you are using. If you can update each accordingly, you should be just fine. When all else fails, you could research the change logs for the discussion module on EllisLab's site and see if it fits your licensed versions.


1

Actually, I figured out the problem. It was a return parameter setting that was sending logged in users to the same page no matter where they came from.


1

Two ways: You could mount s3 using s3fs-fuse^ onto your structure, so EE would experience it as a local file-system and the URL could be the s3 bucket URL. Another way is to use aws s3 sync^^ to synchronise the upload/media folder with s3, that way EE just uses the local file-system and your visitors use s3. ^ https://github.com/s3fs-fuse/s3fs-fuse ^^ ...


1

If you are using Discussion Forum module then you should wrap the forum content into below condition. {if logged_in} {!-- Your Forum Content --} {/if} You can also manage using {if logged_out} condition.


Only top voted, non community-wiki answers of a minimum length are eligible