Am 16.12.2010 18:34, schrieb Morten Kjems:
Den 15-12-2010 09:32, Philipp Gampe skrev:
that means, TYPO3 uses wrong permissions to create files. You can fix
this
in Install Tool.
Thanks for the hint.
I have looked for permission settings but I can't find any.
Where do I look?
The
Am 17.12.2010 09:16, schrieb Bjoern Pedersen:
Am 16.12.2010 18:34, schrieb Morten Kjems:
Den 15-12-2010 09:32, Philipp Gampe skrev:
that means, TYPO3 uses wrong permissions to create files. You can fix
this
in Install Tool.
Thanks for the hint.
I have looked for permission settings but I
I created a new issue and provided a patch:
http://forge.typo3.org/issues/11528
That implementation is working for me.
On 16 December 2010 18:33, François Suter fsu-li...@cobweb.ch wrote:
Hi,
I would like to use some special syntax which would mean ignore this
criteria but cannot find
Hi!
Kay Strobach wrote:
I do not think changing the TER rules solves this Problem.
Please, explain your point of view :)
--
Dmitry Dulepov
TYPO3 coresecurity team member
Twitter: http://twitter.com/dmitryd
Read more @ http://dmitry-dulepov.com/
___
Hi Dimitry,
Am 17.12.2010 10:39, schrieb Dmitry Dulepov:
Hi!
Kay Strobach wrote:
I do not think changing the TER rules solves this Problem.
Please, explain your point of view :)
nothing easier than that:
1) The main Message of TYPO3 is Inspiring people to share
2) Currently most
Hi, François,
Unfortunately only a few are documented. This a well-known shortcoming of
the current manuals. We would be glad if anyone helped filling this gap
actually.
Sorry for not being more helpful.
Okay, I see now.
Anyway, thank you for an answer :)
GPL policy forces company which make huge investiments to not use GPL
sw, simply.
Best approach is FreeBSD policy: use it whatever you like, but use it.
In such a way, usually, a company investing in its work, together with
legacy features, usually returns to FreeBSD a lot of improvements,
Hi
I have a contact form on my site, and I wish to insert the userdata to
the tt_address list, but only if:
- the checkbox with the name 'nieuwsflits' was checked
- the e-mail address does not exists yet in the tt_address table
The former works fine, but how do I implement the later?
Thanks
Hi Tonino,
In this way I'm encouraged to use TYPO3. If I'm forced to go GPL, I will
not use TYPO3.
the core is GPL. That means, that everything which is not usable without
the core or uses core API without any alternative is GPLed as far as i
understand the GPL.
The GPL do not force you to
You are GPL, but closed mind.
Regards,
Tonino
Il 17/12/2010 13:32, Kay Strobach ha scritto:
Hi Tonino,
In this way I'm encouraged to use TYPO3. If I'm forced to go GPL, I will
not use TYPO3.
the core is GPL. That means, that everything which is not usable without
the core or uses core API
Hello Tonino,
i do not understand your last post.
To make you understand i my opinion collected some information from the
official sites (below is the uri/source of the text)
Now, browse around, look in the categories, dive into the great manuals and
enjoy
the beauty of an ordered bazaars
Hi Tonino,
But there has been a decission about the license a long time ago -
perhaps it needs to be discussed - but not in my opinion.
All those examples are ok - you're not forced to publish your extensions
in TER, so your work will be secret - the discussion is about extensions
which are
Tonix, let me say that you seem to have your bible as well: there are
different business models and your point of view applies to one of them.
What is Typo3 as a whole if not an enormous investment?
The problem here is that Typo3 should not be moved by corporate
investments but by developer
A company which works on its own developments must protect its work.
If TYPO3 does not permit that, TYPO3 is not for professionals.
You still miss the point completely.
And there is bad news for you: Since the TYPO3 license forces you to sell your
extensions with a compatible license, all
Il 17/12/2010 15:38, JoH asenau ha scritto:
A company which works on its own developments must protect its work.
If TYPO3 does not permit that, TYPO3 is not for professionals.
You still miss the point completely.
And there is bad news for you: Since the TYPO3 license forces you to sell your
Il 17/12/2010 15:26, Ivano Luberti ha scritto:
Tonix, let me say that you seem to have your bible as well: there are
different business models and your point of view applies to one of them.
Ivano,
I'm saying all models should be accepted and live together.
You are saying only your model must
Am 17.12.2010 16:16, schrieb Tonix (Antonio Nati):
Oh, really? I do not see anything forcing me to sell extensions that
way. The most you can pretend is I cannot load those extensions in TER.
it is the GPL license which forces you to put anything under GPL (or
compatible) license. Any extension
Hi, a small contribution...
1) It shouldn't go the way it goes with Joomla. There you have to buy
(the best) extensions. Am I right?
2) There are people making not that much money with TYPO3, and who are
poor programmers. They contribute to making TYPO3 a popular system by
simply using it for
Hi,
On Fri, 17 Dec 2010 16:39:57 +0100, Vincent Mans wrote:
For the already build extensions that are not maintained, the author can
be asked what he/she wants? And if he/she doesn't respond, the TYPO3
organisation can take the appropriate action. Changing the license or
keeping it to GPL...
And there is bad news for you: Since the TYPO3 license forces you to
sell your extensions with a compatible license, all your clients
already can publish the stuff you did for them without having to ask
you for permission.
Oh, really? I do not see anything forcing me to sell extensions
What I'm saying is that GPL is part of TYPO3 from the beginning and if
you don't wanted to use GPL you should have chosen another CMS. Once you
choose a software you also have chosen its licence. Haven't you?
For what I have understood it's you that are asking TYPO3 to change to
another licence.
Am 17.12.10 17:28, schrieb JoH asenau:
This means that any of your clients could even reserve an extension key in
the TER, upload your extension and make it available to the community for
free. Of course nobody can force them to do so, but the GPL would grant them
these privileges if they
Hey Joey
Well - maybe you should have read the GPL completely before starting to sell
extensions to your clients.
You may believe it or not, but the fact that the TYPO3 Core is GPLed
automatically makes any of your extensions using the TYPO3 core API GPLed by
definition as well. Even if
Well, if you're really concerning about your proprietary extension,
there is a trick. First, find all TYPO3 calls/classes in your extension.
Then create a 'wrapper' library, say (just an example)
function MYSTUFF::makeInstance ($parameters ...)
{
return
For anyone, who will search for same topic, I've made a research by simple
search of '$GLOBALS['TSFE']-register' ($TSFE-register gave 0 results) in
content of all PHP files in TYPO3 4.4. Here is a list with some my
explanations:
class.tx_cssstyled_content_pi1.php
function
Hello list,
i contacted the association to get a clear legal statement
This is the interesting part of the answere:
Peter Proell:
A quick and straight forward statement: Everything is said and written down.
In GPL and when uploading an extension to TER.
A longer statement: As I learned
Il 17/12/2010 16:27, Georg Ringer ha scritto:
Am 17.12.2010 16:16, schrieb Tonix (Antonio Nati):
Oh, really? I do not see anything forcing me to sell extensions that
way. The most you can pretend is I cannot load those extensions in TER.
it is the GPL license which forces you to put anything
Hi,
On Fri, Dec 17, 2010 at 11:06 AM, Tonix (Antonio Nati)
to...@interazioni.it wrote:
Il 17/12/2010 16:27, Georg Ringer ha scritto:
Am 17.12.2010 16:16, schrieb Tonix (Antonio Nati):
Oh, really? I do not see anything forcing me to sell extensions that
way. The most you can pretend is I
http://www.gnu.org/licenses/gpl-faq.html
Regards
Kay
___
TYPO3-english mailing list
TYPO3-english@lists.typo3.org
http://lists.typo3.org/cgi-bin/mailman/listinfo/typo3-english
29 matches
Mail list logo
