Hot answers tagged

33

There is no simple way to do that. You would have to do reverse installation (uninstall) and remove everything manually. If you are using Sitecore Powershell Extensions you could try to create so called Anti-Package. I believe you can do the same with Sitecore Rocks but I am not sure if this is still supported.


23

When I did an upgrade from 7.2 to 8.1 earlier this year, I followed these steps: Setup a new instance of Sitecore 8.1 and configure it according to the documentation. Get my settings/layouts into some sort of source control (using Unicorn or TDS) Apply those settings/layouts to my new instance Compile the existing code against the new version of Sitecore, ...


21

There is no simple way to remove a module in Sitecore once it has been installed unfortunately. The simplest solution is to create an anti-package using either Sitecore Rocks or Sitecore Powershell Extensions. Save the anti-package somewhere and then you can install that which reverse what the install does. If you have already installed the package then it ...


19

I normally try to split DB upgrading from code upgrading. This allows me to run the DB upgrade process of vanilla Sitecore instances where any customisations won't interfere with the db upgrade process. I then upgrade the code as per the SC upgrade guides (and yes this means going through each one). This can take some time because the config changes a lot, ...


19

The answer to this depends on the context of your project. Sitecore's recommendations are to make incremental upgrades for every version and updates as well since your current to the latest you are trying to get upgraded to. This does require a lot of work specially when it's a big jump from 6.5 to 8.2. As already answered here if you are making manual ...


16

No, it does not. Also see here: https://dev.sitecore.net/Downloads/Web_Forms_For_Marketers.aspx It states: Note! Web Forms For Marketers was deprecated with the release of Sitecore XP 9.1 9.0.2 is the last release where WFFM can be used.


13

The WFFM module was significantly re-written in version 8.1+ and allows configuration driven dependency injection out of the box. For example, if you take a look at the /sitecore/system/Modules/Web Forms for Marketers/Settings/Actions/Save Actions/Update Contact Details Save Action then you will see the following item definition: Factory Object Name: /...


13

WFFM and Sitecore forms are quite different in their implementation and the user interface for managing the forms in Sitecore. Both provide a fairly full-featured form building module. Sitecore forms however is a lot slicker to use as a content editor and is built in a much more modern way. However given that it’s still quite new functionally there are some ...


11

After pulling out my non-existant hair, I decided to decompile the Sitecore.Forms.Core.dll. Lowe and behold, there is a check in FormsHandler.cs if the site is not in DisplayMode.Normal to ignore all save actions. In our particular case, the entire site is hidden behind the Sitecore login, therefore to test, it is our common practice to login to Sitecore,...


9

This is a known defect. You should request hotfix 434449 from Sitecore Support. Or just follow these steps: Download the hotfix DLL: a) For Sitecore 8.0: Sitecore.Support.434449.dll b) For Sitecore 8.1 Update 2 or later: Sitecore.Support.434449.81.dll Put the DLL to your website's bin folder. Create a .config patch under App_Config/Include/zzz. a) If you ...


9

Regarding to the following blogpost (https://citizensitecore.com/2016/05/11/wffm-and-cms-only-mode-in-sitecore-8-1/) by default Sitecore saves the WFFM form values in MongoDB after Sitecore 8.0 version. The default connectionStringName is wfm. To make this work on CMS-Only instance you need to overwrite the connectionStringName in the sqlFormsDataProvider ...


8

You should look at jQuery.noConflict(). Use this jQuery method in your JS to avoid conflicts with WFFM included jQuery libs UPDATE: In response to your updated question: no, there is no way to tell WFFM not to use jQuery, but because jQuery registers itself as an AMD module, you should be able to check to see if jQuery is already on the page before you ...


8

No, Sitecore doesn't provide it out of the box, but it's designed to be extended for this purpose. I usually use save actions to send data to third parties: It's pretty simple, as wffm gives you the values of the form, and you just has to implement you logic there. You can find out how here You need to create a class that implements ISaveAction. The entry ...


8

Just because you are logged in does not mean it will treat the user as a contact in xDB. You should check out how to identify contacts. The key being to call Sitecore.Analytics.Tracker.Current.Session.Identify(identifier), where identfier is the username or email.


8

This might be an opinionated question/answer, but I don't think there are real disadvantages. Assuming you have xDB enabled (otherwise the answer is simple and you have to use sql) you should choose between analyticsFormsDataProvider (all in Mongo) or the combinedFormsDataProvider (analytics in Mongo, data in sql). Don't take the sqlFormsDataProvider as ...


7

I already had the same issue and following how you I solved it: Navigate to the following file path: ..\Website\Views\Form\EditorTemplates\FormModel.cshtml Update the following lines: if (Model.SuccessSubmit) { @Html.Raw(!string.IsNullOrEmpty(Model.SuccessMessage) ? Model.SuccessMessage : Translate.Text("Default success message.")) //@Html.Encode(...


7

This is caused by a missing sub-item within the Web Forms for Marketers base form creation process. To fix this until Sitecore corrects the issue: Go into the Content Editor and find your Form Right click on your form and insert a new Form Section (or select it and use your insert options) Give it a name That should get you working again. Until a fix is ...


7

Yes, they are both compatible. WFFM since 8.2 Update-3 (rev. 170413), and EXM since 3.5 (rev. 170810) More information about all modules compatible with Azure Paas can be found here: https://kb.sitecore.net/articles/201557


7

Sitecore Forms and WFFM are 2 different modules that happen to handle the same functionality (forms). There is no migration path available and at the moment there is no mention of anything like that either (on the contrary - when asked the Forms team said this was nowhere on the roadmap because the modules are too different). I have a website running on 9 ...


7

It's not possible without some custom code. The simplest is to create a custom hidden field and store the page URL in this, which will then get submitted along with the other values of the form. You can then use this in your own save actions or the Send Email save action as part of the message body in much the same way as any other form value. I have ...


6

You can try to use the Sitecore Module Package History which is already available on the Sitecore Marketplace. The module enable you to view all the package that have been installed on the Sitecore Instance and also, allows you to uninstall the package. So, for example, if you have install the package WFFM, it will be listed in the aspx page provided in ...


6

This usually happens when that field has been removed since the save action email template was created. Have you renamed/removed any fields since you created it? I'd suggest opening up the save action, removing the [Phone] field, [Message] field etc and then adding them back to the email template using the dropdown of fields. Then saving and trying again. ...


6

@Paul George is correct when he says there is a problem with the MVC Form Rendering and it requires a DataSource instead of a FormID Parameter. Now this causes a big problem, because there is no way of setting DataSource to the @Html.Sitecore.Controller() Helper Method. The only way to solve this is by actually rendering the form with @Html.Sitecore....


6

Be sure to use the MVC Form rendering rather than the Web Forms version, which is just named Form. The Web Forms version of the rendering is not supported for use with FXM. See the documentation: Add an MVC form to an external website with FXM


6

We just had the exact same requirements come up and I solved this using a custom field. Create a new field, CheckboxWithHtml which inherits from the default checkbox and adds a new field: using Sitecore.Form.Core.Attributes; using Sitecore.Form.Core.Visual; namespace MyProject.CMS.Custom.WFFM.Fields { public class CheckboxWithHtml : Sitecore.Form.Web....


6

You exactly can override this. See the solution for that: First of all you need to implement a your custom html helper which should have updated method for rendering the submit button: using System.Text; using System.Web.Mvc; using Sitecore.Forms.Mvc.Interfaces; using Sitecore.WFFM.Abstractions.Data.Enums; namespace Namespace.SC.Extensions { public ...


6

Rather creating a manual drop list field multiple times, I would prefer to create an item repository somewhere in the content tree (Global location is preferable) with all possible Drop List values and on the drop list field in WFFM Form map the Set Item by value to Selecting Sitecore Items rather Manual entering names. Thus you can reuse the same set of ...


6

You can do this using conditional rendering rules. You would need to add the Form to the page twice, but it will only get rendered once. Take this example. I have 2 promo renderings and I want them to render based on the value of a field (could be a checkbox) on an item: Now add a new rule: In the rule, you can use the where the **specific** field **...


6

Go for Sitecore Forms. WFFM is no longer included in 9.1 so that is a dead end... You will need to create your own submit actions (in both options btw) if you want it on this version.. If you can wait just a little longer until the actual release of Sitecore 9.1 (announced for November) you will get an ootb data prefill framework in Sitecore Forms but that ...


5

This is a "bug" in the WFFM module, the Sheer UI form does not set a different text for those headings. In a previous version of WFFM which did not include the "Select Existing Form" option I had added this option back in myself so it is possible to override the behaviour and set the "correct" headings. Make a copy of /sitecore/shell/Applications/Modules/...


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