Hello,
is it possible to have data records (i.e. tt_address items), which are
only editable by specific BE-users?
The problem is, that I have a couple of tt_address items in a sysfolder.
Under the Access panel, I can specify a group or user which has backend
access to it. But that way
Hello,
is it possible to have data records (i.e. tt_address items), which are
only editable by specific BE-users?
The problem is, that I have a couple of tt_address items in a sysfolder.
Under the Access panel, I can specify a group or user which has backend
access to it. But that way either
Hello Xavier
Create folders to group your records and assign proper ACL to them.
okay thanks! I think that's what I'm doing now even though I thought
there's a simpler solution.
Cheers
Martin
___
TYPO3-english mailing list
Am 16.03.2011 08:30, schrieb Xavier Perseguers:
Hello,
is it possible to have data records (i.e. tt_address items), which are
only editable by specific BE-users?
The problem is, that I have a couple of tt_address items in a sysfolder.
Under the Access panel, I can specify a group or user
Hi, I just found one called tm_contentaccess, but I don't think it works
with TYPO3 4.5.2 unless someone can confirm otherwise? It seems to need
a certain skin (skin_grey_2) to be installed as well...
I think i've found a ext a few years ago, which allows ACL on records.
But I didn't know the
You could always hide them with CSS and/or Javascript :-)
Urs
Am 16.03.11 04:50, schrieb Tony Lush:
I have two forms built with Powermail 1.6.2 in TYPO3 4.4.x and each form
has an extra radio button before the defined options when the field is
mandatory. For example:
O
O Option 1
O Option 2
hi,
i use two tt_news list plugins on my page, included into the template by
typoscript.
the first list plugin only displays only 1 entry (the event of the month -
defined by a category).
the second list plugin displays all entries.
everything is fine as long as i don't use a pagebrowser for
Hi,
just FYI:
http://www.google.com/support/webmasters/bin/answer.py?answer=76329
Consider using punctuation in your URLs. The URL
http://www.example.com/green-dress.html is much more useful to us than
http://www.example.com/greendress.html. We recommend that you use
hyphens (-) instead of
Hi,
Page type Standard has no Extended tab. But other page types do
have this tab.
Workaround for now: make a page a Shortcut or Folder, add the
TempaVoila template designs, and then change page type back to
Standard. But this is not how it's supposed to work.
TYPO3 version 4.5.0 till 4.5.2, TV
Vincent Mans schrieb:
Hi,
Page type Standard has no Extended tab. But other page types do
have this tab.
the tv layout you now set on another tab (same as without tv), in german it is
Erscheinungsbild
it is a tv bug that you MUST set this on shortcut pages on extended tab !!!
--
Ralf-René
Hi, so I hacked a solution together by editing
pi1class.tx_ttaddress_pi1.php on line 323. In case someone runs into a
similar problem, this is what I got:
// HACK: UID is our link now ;-)
//$markerArray['###UID###'] = $address['uid'];
$charset =
I've put it on bugs.typo3.org tx_templavoila.
2011/3/16 Ralf-René Schröder ralf.r...@online.de:
Vincent Mans schrieb:
Hi,
Page type Standard has no Extended tab. But other page types do
have this tab.
the tv layout you now set on another tab (same as without tv), in german it
is
I found it!!!
I finally understood why it wasn't working with trnasformations.
I stupidly thought that the $record array passed to the transformation
function would contain source fields, instead it's already named against
destination fields.
Now everything works like a charm, i got tricked
Hi,
with latest TV there is no extended tab, template setting is now in tab
Appearance
vg Steffen
___
TYPO3-english mailing list
TYPO3-english@lists.typo3.org
http://lists.typo3.org/cgi-bin/mailman/listinfo/typo3-english
Hi Nicola,
I finally understood why it wasn't working with trnasformations.
I stupidly thought that the $record array passed to the transformation
function would contain source fields, instead it's already named against
destination fields.
Yes, this is a common mistake. I guess I should add
Yeah, glad too but i found a (in my case) minor problem in the storing of a
field and I don't really know if it even depends on the extension itself.
I'm importing a formatted date time that I convert back to a timestamp
before storing it into the destination table. With much surprise when it's
Hi!
I have a test and a productive site, and I would like to move a page
branch from the test site to the productive one. I can't check Force
UIDs at Import. The site ist bilingual
In the t3d-Export Typo3 tells me it will lose the language information:
sys_language:1 LOST RELATION
Yes I can do that, and I do see a logic to having the extra button in a
required field
Tony
On 3/16/2011 4:48 AM, Urs Bräm wrote:
You could always hide them with CSS and/or Javascript :-)
Urs
___
TYPO3-english mailing list
t3d has never worked well for me. I'd simply export/import the relevant db
tables, if necessary the whole db. Of course you also need to copy any new
files
e.g. in /fileadmin and /uploads. For me, that's less of a hassle than wrestling
with t3d :-).
Matthias
Hi Xavier,
I'm not sure I got ur suggestion.
Do u mean that my server is storing UTC value of my timestamp or am I
completely out of path?
The destination field is merely an int(11) field, what I don't really get is
why after the correct transformation datetime timestamp the latter gets
altered
Hi,
btw my $TYPO3_CONF_VARS['SYS']['serverTimeZone'] is set to 1, shall I
change it to something else? Which are the possibilities?
With serverTimeZone = 1 you set your timezone to GMT+1. A Unix timestamp
has no timezone support (that's was an issue with the Fluid date
viewhelper at the
Aaaah... it looks so different, I totally missed it :-
I can only say: it's not consistent with the other pagetypes.
But I need glasses, that's for sure, after 12 years straing at screens.
2011/3/16 Steffen Kamper i...@sk-typo3.de:
Hi,
with latest TV there is no extended tab,
Dear all,
We cannot send html formatted emails out using the ‘static list’ (this has been
reported as a bug but there is no solution as yet). We are using
sr_feuser_register to register users and have setup Direct Mail to import the
relevant usergroups into a static list.
As we are now
Hi Sara
Please be a little more exact about what doesn't work. What Forge issue
are you reffering to?
Best regards,
Lorenz
Am 16.03.2011 17:58, schrieb Sara Weale:
Dear all,
We cannot send html formatted emails out using the ‘static list’ (this
has been reported as a bug but there is no
This was reported:
http://bugs.typo3.org/view.php?id=17724
The newsletters are only sent out as plain texts and not html when using a
static list.
This seems to be the only alternative to 'plain list' (which obviously we do not
want to use as we require html emails) when importing a website
Am 16.03.11 19:32, schrieb Sara Weale:
This was reported:
http://bugs.typo3.org/view.php?id=17724
The newsletters are only sent out as plain texts and not html when using
a static list.
This seems to be the only alternative to 'plain list' (which obviously
we do not want to use as we
Hi Sara
For your information: I just tested sending a HTML mail to a static list
of FE users. It works fine.
I think you have a misconfiguration. Is it possible that your users
don't have the flag Send direct mail as HTML set? If so, no mail will
be sent (if type of mail is HTML only) even
27 matches
Mail list logo
