In order to allow BE users to set Access options for content elements, I
had to make sure that the user (or usergroup) has the group storage
folder mounted. I also made sure the workspace they use had the group
storage folder defined as a mount as well, but I'm not sure that was
necessary.
Regards
I am having the same issue Stefanos described.
What needs to be set in order for normal FE users to be able to set FE
group access to pages and content elements?
As near as I can tell, admin access helps a lot. No admin users seem to
have this problem. They can see all fe_groups available in the
It's a known bug with recent Firefox versions:
http://bugs.typo3.org/view.php?id=11009
Painful, but fixable.
ak
Lamb, Brian wrote:
> Greetings all,
>
> I am having an issue with creating links in the RTE. All of a sudden, typo3
> is prepending all of my external links with http://typo3. For
Normally, you need to modify the TypoScript of your template to do this.
However, this extension is quicker/simpler and it might work for you:
http://typo3.org/documentation/document-library/extension-manuals/kb_customhead/0.0.1/view/
ak
Ryan Bilesky wrote:
> I am wanting to add some functionali
Hello,
In a similar situation I am having trouble with the page tree due to
CoolURI. CoolURI relies on the domain name being the same so links break
in the tree when I use multiple domain records.
Has anyone accomplished dynamic content replacement based on domain
along with the CoolURI clean URL
