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 **...
It's definitely not as simple as Vlad makes it out to be.
Officially, Sitecore does not support this. You can mix and match MVC and WebForms in the same project, but only on a page-by-page basis. So either the page executes as Webforms (with Webforms components) or as MVC with MVC components.
There's been a few attempts to wedge around this, but I would ...
To answer your question, PaaS is simply another way of saying that an IIS site exists that allows you to run a website. Said differently, using the Sitecore Azure Toolkit to deploy a vanilla instance of Sitecore 9.0.2 to Azure PaaS and then deploying your code base through a WebDeploy package should be sufficient to utilize PaaS.
Things to consider when ...
This should be added inside sitecore node.
<sc.variable name="webDAVPrefix" value="/sitecore_files"/>
Look at sitecore.config for some uses.
I ended up getting it working, but not using the RenderControl() method. It turns out, that I could just call the GetControl() to get the control for the sublayout afterall, and append that control to the child controls for the actual view. Moreover, I found that it was necessary to set the datasource, before calling the GetControl() method:
var renderings =...
While this is an example of rendering a Controller Rendering, I believe it will help you - the basic principles should be the same. Specifically I think, entering a RenderingContext is what you might be missing.
public virtual HtmlString RenderItem(string idOrPath, string controller, string action)
When you directly set up your IIS site to use your folder where the Visual Studio solution placed it can happen because of the Rebuild. Rebuild means cleaining up your bin folder and only take the assemblies which are in your Visual Studio project.
So if the Sitecore.Form.Core.dll is not used in your project then the Rebuild removes it. If you setup the ...
As mentioned here already, use the Sitecore Express Migration tool: https://dev.sitecore.net/Downloads/Express_Migration_Tool/20/Express_Migration_Tool_20_Initial_Release.aspx
Note that this will migrate the data to a new clean instance (always use clean instances when upgrading).
Onces your databases are migrated to the new version, you can update the ...
This is still possible today, I just tested and confirmed with SC8.2 update 4. You can still modify Global.asax and add Application_Error method.
However, per practically every best practice post out there, you should NOT change the files that come from Sitecore. It could impact your ability to upgrade, etc. Plus, per old Sitecore John posts there are many ...
This was just because caching had been mistakenly added to the Sublayouts that use dynamic placeholders.
Edit (further explanation):
We have a set of sublayouts/renderings that are used for page structure, and just contain (dynamic) placeholders - i.e. "one column row", "two column row" etc. They are just used to add actual components into. Adding caching ...
I had same question to support if Wffm Mvc and Wffm Web Forms can coexist in a Mvc Application.
Their answer was they can coexist but with limitation :
for one item - use the CSHTML layout, views, View Renderings and Controller Renderings;
for another item - in the same solution, presentation can be used with the ASPX layout, ASCX controls and XSLT ...
No one followed up so I will answer what I found. This answer applies to projects outside of the Sitecore instance. The problem was I used the NoReferences versions of the Sitecore libraries. It turns out that if you want reliable Intellesense, then use the libraries with references making sure to add from the NuGet Sitecore repo the correct revision for ...
No, the OOTB Dynamic Placeholders in Sitecore 9+ does not support Webforms. The implementation is in the Sitecore.Mvc namespace, a.k.a. this is an MVC-only implementation.
If you need to support Webforms then you would need to fallback to rolling your own or using one of the community implementations (such as Fortis Dynamic Placeholders), but you may need to ...
I've done the same on two different projects.
From my experience it should be fairly straight forward to update your webforms and normal usage of the Sitecore API. There might be minor changes, but it shouldn't take too long.
All of your hookins into pipelines etc. might still compile. But you will want to check if it's still needed. It may be a fixed bug, ...
The Sitecore controls are looking for the fields on the context item. Since you're using a data source you need to pass that item into each of the controls using the Item property on the control.
<sc:Image ID="imgTitleImage" Field="Title Image" runat="server" Item="DataSourceItemHere" />
When you want to modify the output of a particular field, your best bet is to override the renderField processor of the field type you're targeting.
<processor type="Sitecore.Pipelines.RenderField.GetImageFieldValue, Sitecore.Kernel"/>
Create a new class that inherits from the existing class:
public class ...
You can look up the referrers of the specific user control since it's an item in Sitecore (rendering/sublayout) using the Link database.
For a quick check, you can take a look at the Navigate ribbon > Links
If you want a report-like list, it might be easiest to use Sitecore Powershell Extensions to get a list of all referrers in an exportable format - ...
I'd recommend adding it to a patch file (which will add it to the main compiled sitecore node). You can place the patch in your App_Config/Include folder in the Website root. (Ex: App_Config/Include/Settings.config)
Your list of values for states is not valid and that is causing you trouble.
Instead of South Carolina and South Dakota you are using same value "South" and that's why you have duplicates. "Carolina" and "Dakota" are not part of value.
Text part / Display name is rendered correctly. Only problem is with Value field.
You have the same also for states that ...
For anyone who finds this in future: My problem was the 'Author' role being applied to my user. For whatever reason, this conflicts with WFFM. Removing the role has no noticeable effects on my users and seems to have resolved the issue.
I can confirm that it works on Sitecore 7.2 as well as Sitecore 8.2 (we have upgraded along the way).
We have a multisite installation with 4 sites running MVC and the last site being Webforms. We're using WFFM on 1 MVC site and the webforms site without any issues (we're not sharing any specific forms between the 2 sites though).
Application_Start was made internal, but you can still use Application_Error (if you want) in a WebForms project.
Just make sure that you global.asax overrides the one from Sitecore (Sitecore.Web.Application) otherwise you'll break the site.
Sitecore 8.2 still supports both MVC and Webforms. However, a page should be either completely webform or completely MVC. This should not be a blocker in your case as you will be upgrading existing application on Sitecore 8 webforms
Add the UserControlRenderer and GetUserControlRenderer classes to your solution, and patch the mvc.getRenderer pipeline with mvc.usercontrolrenderer.config and you’re good to go.
The source can be found at https://github.com/efocus-nl/sitecore-mvc-usercontrolrenderer
Update panels have their UpdateMode property set to Always by default, so they'll fire on any post back, even from another update panel. You'll want to set it to Conditional. Conditional will update only if a child control or child update panel is the thing triggering the post back.