Search:

Actually, V2 extensions can be used in V3 with a minor adjustment – you have to register all files by yourself. However, the newly included devtools extension will generate the registration file for...

IMO the PHPSESSID-Cookie is exempt from this regulation as it is needed technically (esp. for forms).

What about a Google Translate Add-On? I guess you're either using Firefox or Chrome; there should be extensions to both of them.

We need some way to remind the ones creating issues in German to...

I'm certianly no HTTP expert, but those lines should be responsible for the error (at least to some extent):


Vary: Accept-Encoding,*
[…]
Transfer-Encoding: chunked
X-Cnection: close...

http://php.net/ob_gzhandler

Please check your PHPinfo for zlib.output-compression, Zlib and GZip.

The var corresponding to the setting is $GLOBALS['TL_CONFIG']['enableGZip'], searching the code for this should reveal all important parts of the code.

Does it help splitting up the .htaccess between frontend and backend, i. e. using a separate .htaccess for the backend (in the folder /contao/)?

Might be an Apache httpd 1.3 issue. The current .htaccess works great with the current Apache httpd 2.2 ;-)

Though it's good to know it works. I think you can file a ticket for having the "old"...

Most likely the AddEncoding does the trick (it should be the equivalent of "SetOutputFilter DEFLATE" ll. 34 and maybe "Header append Vary Accept-Encoding" ll. 46 in the current .htaccess).
...

The world (of manuals) would be easier if the world consisted of more people like you. But it doesn't.


But I agree, using the manpower for a proper online documentation first would be better.

The problem is: People still want to read them and learn from books. Computer screens are still not suitable for extensive reading (except ink screen). Yes, you can have a searchable documentation on...

My last take on my suggestion: Of course we can't wait forever. And, having collaborative editing (well, any editing at all) we can actually update the book adding the latest changes (which won't be...

The team shouldn't be infinitely big but rather small. That should solve big parts of both problems (though they cannot be eliminated completely – but hey, we got time and don't need to rush!).

...

Why not crowdsource the translation of one of the Contao books? There should be enough people who can translate well between English and German, and we can have native English speakers for proof...

Either, you're not allowed to set these options, or you cannot set those settings at all because of a missing Apache httpd module.

There's gonna be a (privately organized) Developer Conference in Germany some time in November. As far as I can tell, they will talk a lot about the framework though I doubt there will be a...

Maybe it's not enough. Maybe it's something else. But we're pretty sure the problem involves the compressed version of TinyMCE, maybe it's the version itself, maybe the browser (cache), maybe the...

Actually, there seems to be some "misunderstanding" between browser and server and some software running on the server side when mod_deflate is missing. We're not 100% sure about that but it's most...

No, those are the PHP compile parameters. I was looking for the Apache web server settings found in the httpd.conf, probably at /etc/apache2/. But as I said, you're likely not to see any of those as...

Nah, I need the Apache config, which you probably don't get unless you're your own server provider ;).

Can you PM me credentials and a link for the backend? I'd like to check the headers etc. once...

I assume Fx is less fault tolerant than other browsers in this case.

The PHP info setting doesn't say much, I acutally need ALL Apache configs. Though .htaccess should be a good start.

OK looks like we finally got it: In some configurations, there is a problem with the compressed version of TinyMCE.

Please check your server whether there is DEFLATE support and it is enabled...

Yeah, please report it and state that you're not having trouble with the TinyMCE demo (btw, does this one use GZ compression?).

I think you only need the typolinks folder from the current package if you want to install the plain TinyMCE version. Though there might be some changes to the config inside the TinyMCE plugin folder...

I think I had a similar problem with TinyMCE before. Can you please check whether the same "blank" screen appears on the TinyMCE demo page?

Also see my TinyMCE ticket.


Edit: After some update...

HTTP status should be ok.

Looks like the JS errors render the site unusable OR TinyMCE generates an overlay – is the blank screen completely white? Are you using the contextmenu extension of...

One more question: What browsers + versions do you use, did you try another browser?

The Context menu is a new function. It enables right-clicking on some edit icons where you can chose to edit the elements or the header.

Well, you said that the source code of the blank pages is...

You posted a JS error indicating that a function is not defined, hence the question.

Though blank screens shouldn't be evoked by JS errors but rather PHP errors.

My tip is that occasionally...

Uhm … you might wanna have a look at [efg] and/or [catalog]. Generally, it's possible to do what you want to do in Contao, though I can't tell you how much effort it will be (i. e. configuring...

Did you disable MooTools?

As IE7 is not as bad as IE6, dropping support for IE7 won't make a site completely unusable, it'll just look different. I actually do have a site I built about a year ago which cannot be used in IE6...

As IE7 never really stuck around, you might be able to ignore it completely. IE7 upgraders updated to IE8 very fast (for the most part, according to my stats).

According to w3schools, IE7 is...

You might want to have a look at the catalog extension.

As they change not very often, you should be on the safe side. Otherwise you can provide specialised modules that implement the legacy modules.

Just took a quick look into the diff file – most of your proposed changes can be accomplished without touching any core file. Please use an extra extension (i. e. the one you already created) to...

This looks awesome! Looking forward to it :)

thyon, the WIKI is run by some of the community members, neither Leo nor the Contao team. I'm pretty sure there's nothing that will be changed with the current WIKI (except the design).

I just saw that you're using TYPOlight 2.7.1. Please update to 2.8 or Contao 2.9 and check whether the problem appears again.

Edit: Sorry, never mind, looked at a different post.

Looks like either your server or some auxiliary hardware (gateways, routers) does have a lookup problem. You should try and contact your hoster.

It says there is a temporary error. If the error continues to show up in the next 24h, please notify us.

Still, Contao should catch every SOAP exception to make the backend usable even if there is...

If I were you I would use the CSS3 'border-radius' and vendor specific ('-moz-', '-webkit-', '-o-' prefix) properties to round a box's corners. It'll leave out IE 8 and older users (though users of...

The German part of the wiki is filled pretty quickly. And we're not filling it by saying it won't work out.

The WIKI is still waiting for someone to dress it nicer ;) You're welcome (and encouraged) to create a new design.


The WIKI does have the advantage that everybody can add and edit text. A...

Anything remarkable in /system/logs/error.log? Activated "Show error messages"?

Article -> Content Element "Text".

BTW, the German Contao Community may be the better contact point for you.

If you don't know a thing about PHP, you might not be able to help us (except you'll let someone access your server).

Ever tried to use FancyUpload on another computer? Does the original...

Then please provide us with some debugging information.

Nah, the #400 is thrown by Contao – FancyUpload just instantiates a HTTP connection and listens for the return code. Check the files I mentioned. A simple exception or error logging should reveal the...

Maybe Cookies are disabled in the other browsers?

Try to find out where the #400 error is thrown (should be somewhere in upload.php, initialize.php, or DC_Folder.php). That'll help us debugging it.

This is most likely because your browser inserts your backend password (which you saved for the login page) into the password field. There is a HTML5 attribute which prevents auto fill-in – maybe...

You can repair the table in PHPMyAdmin. Go to the database table overview, mark the desired table(s) and choose repair method from the actions dropdown.

As far as I experienced, BE_USER_LOGGED_IN is 'true' in the frontend, only when you are previewing the site while showing disabled items.

There have been several threads about this. This shouldn't be a problem, as long as your hardware is strong enough.

Seems like your syncing wasn't very efficient and outdated files haven't been updated ;).

Did you consider using the LiveUpdate-Feature? It's ubereasy and very efficient (and not at all costly).

Looks like this file hasn't been updated. I updated one 2.8.2 yesterday and it displays the correct version.

You should run the typolight-check to see if the other files have been updated.

Could be catalog or autolink. Dunno how they work, though …

Or your IP might also change due to using the mobile network. Make sure it stays the same (you might want to use VPN tunneling – dunno for sure if this works) or disable the IP check (increased risk).

What extensions are installed, do you use a custom one? Looks like your Linking is somehow flawed. Certainly doesn't look like native TYPOlight URLs.