Gravatar for timsodhi@health.usf.edu

Question by timothevs, Nov 24, 2015 10:28 AM

Allowing non-admin users in Sitecore to create search pages

Hello,

We'd like to allow some of our Sitecore editors to add Coveo search to some of the pages in the CMS. They are able to create pages based off the template, but when they try to edit the search properties, they get an error in the page popup in the page edit mode.

We have been able to get around this by granting them admin access, but this is less than ideal. What permissions do we need to grant these users so that they can administer search on the new pages?

Thanks!

Gravatar for jflheureux@coveo.com

Comment by Jean-François L'Heureux, Nov 24, 2015 1:09 PM

Hi,

This is a very good question. I was not aware of a permission problem in this area of Coveo for Sitecore. I'll need to investigate this in detail but I don't have a lot of time these days.

If you're a paid customer of Coveo for Sitecore, it would be faster for you to open a support ticket. It would be escalated to the development team to be addressed faster than it could be on this Q&A website.

Let me know if you open a support ticket.

Thanks, Jeff

Gravatar for timsodhi@health.usf.edu

Comment by timothevs, Nov 24, 2015 1:16 PM

Thanks Jeff, we have opened a support ticket.

1 Reply
Gravatar for dberube@coveo.com

Answer by Dominic Berube, Nov 25, 2015 3:35 PM

Hi,

We were able to reproduce the issue and are getting an error similar to:

[Exception: The field "c502bdeb-f5da-4ad0-8095-d7cc1d0e1eec" does not exist.]
   Coveo.UI.SitecoreUtilities.GetCoveoFieldType(IDatabaseWrapper p_Database, String p_FieldId) +654
   Coveo.UI.Controls.SortFieldPicker.IsSortableField(String p_FieldId) +79
   Coveo.UI.Controls.SortFieldPicker.HasSortableFields(String p_TemplateId) +578
   Coveo.UI.Controls.SortFieldPicker.GetTemplateItems() +246
   Coveo.UI.Controls.TemplateFieldPicker.LoadTemplateList() +143
   Coveo.UI.Controls.TemplateFieldPicker.OnLoad(EventArgs p_Args) +262
   System.Web.UI.Control.LoadRecursive() +71
   System.Web.UI.Control.LoadRecursive() +190
   System.Web.UI.Control.AddedControl(Control control, Int32 index) +257
   Sitecore.Web.UI.Sheer.ClientPage.AddControl(Control parent, Control control, String placeholder) +291
   Sitecore.Shell.Applications.ContentEditor.EditorFormatter.AddEditorControl(Control parent, Control editor, Field field, Boolean hasRibbon, Boolean readOnly, String value) +367
   Sitecore.Shell.Applications.ContentEditor.EditorFormatter.RenderField(Control parent, Field field, Item fieldType, Boolean readOnly, String value) +1495
   Sitecore.Shell.Applications.ContentEditor.EditorFormatter.RenderField(Control parent, Field field, Item fieldType, Boolean readOnly) +238
   Sitecore.Shell.Applications.ContentEditor.EditorFormatter.RenderField(Control parent, Field field, Boolean readOnly) +398
   Sitecore.Shell.Applications.ContentEditor.EditorFormatter.RenderSection(Section section, Control parent, Boolean readOnly) +369
   Sitecore.Shell.Applications.ContentEditor.EditorFormatter.RenderSections(Control parent, Sections sections, Boolean readOnly) +179
   (Object , Object[] ) +123
   Sitecore.Pipelines.CorePipeline.Run(PipelineArgs args) +365
   Sitecore.Shell.Applications.ContentManager.Editor.Render(RenderContentEditorArgs args, Control parent) +534
   Sitecore.Shell.Applications.ContentManager.FieldEditorForm.RenderEditor(Border parent) +354
   Sitecore.Shell.Applications.ContentManager.FieldEditorForm.UpdateEditor() +319
   Sitecore.Shell.Applications.ContentManager.FieldEditorForm.OnPreRendered(EventArgs e) +37

The problem was because the user didn't have access to all the fields of all the templates.

We fixed the code and it will be available in the February or March 2016 release of Coveo for Sitecore.

Ask a question