function readOnly(count){ }
Starting November 20, the site will be set to read-only. On December 4, 2023,
forum discussions will move to the Trailblazer Community.
+ Start a Discussion
wintamutewintamute 

Issue with accessing data from licensed managed package on sites

Hi,

 

We got an issue with accessing data from a Visualforce page contained in Sites. The data that should be displayed is from a custom object contained in a licensed managed package. This worked fine until the package was upgraded to a new version which required licesing.

My guess it's something related to the sites user not having a license for that package (doesn't show in the user list for assigning licenses).

 

The Problem: the visualforce page called when normally loged in with a licensed user works as expected (via /apex/Pagename). When called from outside via domainname.force.com/Pagename it shows only empty values. The page iterates over a list of objects with apex:repeat. I get as many empty objects as I should get, so that part works. Just the values are missing, using {!object.field__c} syntax.

 

Any hints, pointers? Maybe a bug? I couldn't find anything regarding that odd bevavior.

 

The page code:

 

<apex:page cache="false" controller="XMLlistingController" contentType="application/xml"><?xml version="1.0" encoding="UTF-8"?>
<LocationList>
<apex:repeat value="{!locations}" var="location">
<Location__c>
<Id><apex:outputText value="{!location.Id}" /></Id>
<Name><apex:outputText value="{!location.Name}" /></Name>
</Location__c>
</apex:repeat>
</LocationList>
</apex:page>

 

The controller simply queries for the Location__c custom object and returns a list.

 

Output from /apex/LocationPage

 

<LocationList>
<Location__c>
<Id>
a0B80000003uOfiEAE
</Id>
<Name>
Example Location
</Name>
</Location__c>
</LocationList>

 

output from domainname.force.com/LocationPage:

 

<LocationList>
<Location__c>
<Id/>
<Name/>
</Location__c>
</LocationList>

 

edit: Just to underline it's not a basic permission problem:

The sites user has all necessary permissions on that object, also field level security settings are fine. It worked before licesing for that package was turned on.

 

 

 

 

 

Message Edited by wintamute on 09-18-2009 01:06 PM
Message Edited by wintamute on 09-18-2009 02:07 PM
Best Answer chosen by Admin (Salesforce Developers) 
ForcecodeForcecode

We had the same problem.

 

I think you use a User License for the package, no Unlimited License, right ?

 

Read this.

All Answers

ForcecodeForcecode

We had the same problem.

 

I think you use a User License for the package, no Unlimited License, right ?

 

Read this.

This was selected as the best answer
wintamutewintamute

Yeah, that seems to be the problem, we're not using the site wide licensing. I already voted on your idea.

 

My initial search on the discussion board didn't turn up anything useful.

 

Thanks for the information.