[Amal Vellappillil]

Awesome, thank you for working on it.

[Amal Vellappillil]

Hi Alex,

Were you able to look into this?

[Amal Vellappillil]

Sounds good and thank you for looking into it.

[Amal Vellappillil]

Hi Alexander,

Thank you for your reply. I understand it’s possible to create a variable and use it an email template like {var:variableName}. I was just curious if there was a way to bypass that step of defining a variable and setting the variable.

Ex:

var fullName = "";
function setFullName(firstName, lastName) {
    fullName = firstName + " " + lastName;
}

function getFullName(firstName, lastName) {
    return firstName + " " + lastName;
}

Instead of calling the setFullName function first then using the variable name fullName in the email template, I was wondering if there was a way to just use getFullName itself in email template.

Hope I made things clear.

[Amal Vellappillil]

Hi Alex, i found what the actual problem is. In order for emails to work properly, the user needs to have at least contribute rights to the site collection or DFFS_Email list depending on the method being used.

Hope this limitation can be worked on to make it work without giving users this much permission. Is it possible to have DFFS plugin work under a specific user that way DFFS doesnt need to rely on users permission?

[Amal Vellappillil]

Same with me Kasey. I ended up moving the SPJS document library to the site collection and gave view rights to the top level site in the site collection. After that i havent gotten the error message. Whatever we do, it seems like the only solution is to give access to the root site in the site collection to users to not get this error. Not how i wanted to fix the issue, but since there is no other solutions, I have to deal with it for now.

This seems like a bug to me since DFFS allows you to install in just an individual site but also in a site collection.

Thank you for sharing your experiences in this thread. Hope the team will be able to take a look at this issue and get it resolved.

[Amal Vellappillil]

Hi Alex,

I tried the first command you recommended and it returned true. I tried enabling the print active tab option and sending an email, but it failed returning back the same error message as i mentioned above. Let me know what i can do next.

Thank you,
Amal

[Amal Vellappillil]

DFFS v4.4.2.5

[Amal Vellappillil]

Hi Alex, I see that i am getting a lot of unauthorized request (401 status code) for all of the DFFS files. The user has full control to the SPJS document library and the list. I am very confused at this point.

[Amal Vellappillil]

Hey Alex, is there anything else you recommend? I really need that annoying pop up to go away. Please help.

[Amal Vellappillil]

Hi Alex, I looked for those settings and “Read” has all of the ones you mentioned as allowed.

[Amal Vellappillil]

Hi Alex,

I did as you requested and I see the scripts are being loaded from my subsite instead of site collection root. But I am still getting the same Access Denied error pop up. The user has read rights to the whole site. What needs to be done now? Thank you for helping me so far.

[Amal Vellappillil]

Hi,

Is moving the installation from site collection to site as simple as following?
– Create a SPJS document library on the root of the site and copy the DFFS folder there?

Questions?
– Can I still keep the SPJS folder in the site collection root?
– Will I loose all the form configurations/modifications I have done so far? Is there a way to back up the work I have done so far?

Thank you for helping out so far.
– Amal Vellappillil

[Author]

Posts