Adobe Usergroup dreamworker.de

Dreamweaver CS6 Bedienfeldgruppen per Doppelklick schließen - geht nicht mehr (nur bei mir?)

Killertitte — Wed, 16 May 2012 12:46:05 GMT

Guten Tag an alle,

arbeitet schon jemand mit CS6 und kann das mal prüfen?! Das wäre sehr nett. Bei mir funktioniert der Doppelklick auf den oberen Rand einer Bedienfeldgruppe nicht :(. Bisher konnte man die immer per Doppelklick ausblenden.

Speziell ärgerlich ist das, wenn man Dateien durchsucht - was ich sehr häufig tue - dann erscheint unterhalb des Coding-Fensters immer die Gruppe mit den Ergenissen. Um diese wieder auszublenden, muss ich jetzt immer auf das kleine Icon klicken und 'manuell' ausblenden.

Oder habe ich vielleicht was falsch gemacht beim 'Übernehmen' der Einstellungen aus der vorigen Version. Könnte gut sein, das ich da was vergnaddelt habe. Könnte mir vielleicht jemand bitte eine kurze Rückmeldung geben. Dann wüsste ich, ob eine Neuinstallation Abhlfe schafft.

Vielen Dank!

MJ

Dreamweaver CS5 Ärger mit PHP

wolly — Wed, 16 May 2012 07:33:27 GMT

Hallo,

ich hab das Problem, dass meine PHP Seiten nicht angezeigt werden.

Im Klartext:

- ich verbinde mich mit dem Remote Server auf dem meine Dateien liegen
- nun rufe ich eine Seite auf (stratseite.htm) - alles noch ok
- nun hab ich die Seite am Bildschirm (Entwurfansicht)

jetzt der Fehler !!!

- die Bereich in denen PHP Daten stehen sollten sind mit einem Zeichen (PHP) gefüllt
- gehe ich auf Live Ansicht wird "Server nicht gefunden" angezeigt.

Ich bin leider nur Anfänger und würde mich über eine Behebungsbeschreibung seh freuen!

Danke und beste Grüße aus Salzburg
Wolly

Zusatz: im IE und Firefox wird alles richtig angezeigt !!!

Technologie Weitreichende Neuerungen für interaktive Web-Anwendungen mit Adobe ColdFusion 10

dreamworker.de — Wed, 16 May 2012 07:20:12 GMT

HTML5-Integration und weitere neue Features sorgen für einen Performance- und Produktivitätsschub München – Adobe® ColdFusion® 10 ist ab sofort verfügbar. Die serverseitige Technologie ermöglicht Entwicklern die Erstellung von dynamischen und interaktiven Web-Anwendungen für Unternehmen auf Basis der Java™ *EE Plattform. ColdFusion 10 unterstützt ab sofort HTML5 und steigert die Performance durch die Integration von Tomcat und [...]

Weiterlesen...

Anfänger: Frage zum Navigationsmenü

lautdenken — Tue, 15 May 2012 09:59:05 GMT

Ich würde gerne ein Navigationmenü wie auf dieser Seite nutzen: www.vr.de
Nur dass das Bild zum Thema vielleicht noch etwas geschmeidiger wechselt. Aber dass man die Navigation komplett im oberen Abschnitt belässt.

Kann man ein solches Menü mit Dreamweaver CS4 oder CS5 Boardmitteln erstellten oder verwendet man hier Flash oder ähnliches.

Gibt es evtl. kostenfreie Navigationsmenüs die man nur noch einbinden muss?

Danke für eure Hilfe!

Adobe rudert zurück und behebt Lücken in Creative Suite 5.x

simplicissimus — Sat, 12 May 2012 17:29:30 GMT

Die Sicherheitslücken bei Photoshop und Illustrator (Creative Suite 5.x) werden nun doch behoben.
Anfangs verließ das Unternehmen verlauten, dass sich die Anwender nur durch ein (natürlich) kostenpflichtiges Update auf die Creative Suite 6 absichern können.
Nach zahlreichen Protesten will Adobe nun doch einen Patch zur Verfügung stellen:
http://www.heise.de/ct/meldung/Photo...h-1574358.html

Veranstaltung Captivate eSeminare Wochen

dreamworker.de — Fri, 11 May 2012 15:30:03 GMT

Captivate eSeminare Wochen | Ab 23. Mai bis 27. Juni 2012

Weiterlesen...

Technologie Adobe Muse ab sofort erhältlich

dreamworker.de — Fri, 11 May 2012 12:00:45 GMT

Adobe Muse ist ab sofort verfügbar. Die Software ermöglicht es Designern, Webseiten zu erstellen, ohne Code schreiben zu müssen.

Weiterlesen...

Technologie Adobe Creative Cloud ab sofort verfügbar

dreamworker.de — Fri, 11 May 2012 09:50:31 GMT

Die Adobe Creative Cloud ist ab sofort verfügbar. Sie ermöglicht Kreativschaffenden einen neuartigen Zugang zu Adobes Werkzeugen und Services.

Weiterlesen...

Dynamisch: Dateisystem visualisieren mit Tool?

birdy1964 — Wed, 09 May 2012 10:28:14 GMT

Hallo zusammen,

folgende AUfgabenstellung:

Ich habe auf dem Server eine Dateistruktur mit Unterordnern und Dokumenten (z.B. .pdf, .xls, ...). Nun suche ich eine Möglichkeit diese Inhalte via Webseite sichtbar zu machen. Dabei sollen jedoch keine fixen Symbole für Ordner zu sehen sein, sondern (im Idealfall) frei definierbare Symbole bzw. nur ein Text, der wenn man auf ihn klickt in den Ordner führt.

Beispiel: Im obersten Verzeichnis gibt es drei Unterverzeichnisse - Die Anzeige wäre dann:
> Ordnername1
> Ordnername2
> Ordnername3

Beim Klick auf Ordnername1 kommt man in das zugehörige Verzeichnis u.s.w.

Wenn Dateien im Verzeichnis stehen kann man diese durch anklicken anzeigen.

Wenn man per ftp weitere Verzeichnisse/Dateien in die Verzeichnisstruktur kopiert, muss sich die Anzeige nach einer Seitenaktualisierung entsprechend anpassen (feste Verlinkungen gehen also nicht).

Fazit: Funktion wie bei FTP nur mit Lesen und mit definierbaren Symbolen und Texten ...

Wie kann man sowas realisieren? Gibt es ein Tool hierzu? Script?
Danke und Gruß

Birdy

DW Spry Tabbed Panel

DenisCGN — Wed, 09 May 2012 08:48:54 GMT

Hallo zsuammen,

kann ich per Javascript irgendwie feststellen, wenn ein bestimmtes Panel aufgerufen wird? Ich möchte genau dann eine Fuktion ausführen.

Geht sowas?

Grüße,
derDenis

W3C Validator Probleme nach Flash Movie Einbindung mit CS3

Cosmic Bandido — Tue, 08 May 2012 11:15:34 GMT

W3C Validator Probleme nach Einfügung eines Flashmovies
Hallo zusammen,

Ich arbeite mit Dreamweaver CS3 und heutefügte ich ein Flashmovie ein.
Eigentlich läuft der bei der Vorschau ganz gut. Habe mit FF und Chrome getestet.

Jetzt habe ich die Seite im W3C Validator unter http://validator.w3.org/check gecheckt und bekam eine Menge Fehler Meldungen, die mich überfordern.
Kann mir jemand von euch helfen?

Hier mal die Infos zum W3C Check und mein Html Code.

Zitat:

Validation Output: 31 Errors

Line 19, Column 51: character "&" is the first character of a delimiter but occurred as data
…isIE = (appVersion.indexOf("MSIE") != -1 && userAgent.indexOf("Opera") == -1); ✉
This message may appear in several cases:
- You tried to include the "<" character in your page: you should escape it as "<"
- You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&", which is always safe.
- Another possibility is that you forgot to close quotes in a previous tag.
Line 19, Column 52: character "&" is the first character of a delimiter but occurred as data
…isIE = (appVersion.indexOf("MSIE") != -1 && userAgent.indexOf("Opera") == -1); ✉
This message may appear in several cases:
- You tried to include the "<" character in your page: you should escape it as "<"
- You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&", which is always safe.
- Another possibility is that you forgot to close quotes in a previous tag.
Line 23, Column 19: character "&" is the first character of a delimiter but occurred as data
if (plugins && plugins.length > 0){ ✉
This message may appear in several cases:
- You tried to include the "<" character in your page: you should escape it as "<"
- You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&", which is always safe.
- Another possibility is that you forgot to close quotes in a previous tag.
Line 23, Column 20: character "&" is the first character of a delimiter but occurred as data
if (plugins && plugins.length > 0){ ✉
This message may appear in several cases:
- You tried to include the "<" character in your page: you should escape it as "<"
- You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&", which is always safe.
- Another possibility is that you forgot to close quotes in a previous tag.
Line 42, Column 20: character "<" is the first character of a delimiter but occurred as data
if (flashVer < reqVer){ ✉
This message may appear in several cases:
- You tried to include the "<" character in your page: you should escape it as "<"
- You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&", which is always safe.
- Another possibility is that you forgot to close quotes in a previous tag.
Line 100, Column 206: cannot generate system identifier for general entity "MM_ComponentVersion"
…'FLVPlayer_Progressive','flashvars','&MM_ComponentVersion=1&skinName=Corona_Sk… ✉
An entity reference was found in the document, but there is no reference by that name defined. Often this is caused by misspelling the reference name, unencoded ampersands, or by leaving off the trailing semicolon (;). The most common cause of this error is unencoded ampersands in URLs as described by the WDG in "Ampersands in URLs".
Entity references start with an ampersand (&) and end with a semicolon (;). If you want to use a literal ampersand in your document you must encode it as "&" (even inside URLs!). Be careful to end entity references with a semicolon or your entity reference may get interpreted in connection with the following text. Also keep in mind that named entity references are case-sensitive; &Aelig; and æ are different characters.
If this error appears in some markup generated by PHP's session handling code, this article has explanations and solutions to your problem.
Note that in most documents, errors related to entity references will trigger up to 5 separate messages from the Validator. Usually these will all disappear when the original problem is fixed.
Line 100, Column 206: general entity "MM_ComponentVersion" not defined and no default entity
…'FLVPlayer_Progressive','flashvars','&MM_ComponentVersion=1&skinName=Corona_Sk… ✉
This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.
Line 100, Column 225: reference not terminated by REFC delimiter
…ive','flashvars','&MM_ComponentVersion=1&skinName=Corona_Skin_3&streamName=sch… ✉
If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.
Line 100, Column 225: reference to entity "MM_ComponentVersion" for which no system identifier could be generated
…ive','flashvars','&MM_ComponentVersion=1&skinName=Corona_Skin_3&streamName=sch… ✉
This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.
Line 100, Column 205: entity was defined here
…,'FLVPlayer_Progressive','flashvars','&MM_ComponentVersion=1&skinName=Corona_S…
Line 100, Column 228: cannot generate system identifier for general entity "skinName"
…','flashvars','&MM_ComponentVersion=1&skinName=Corona_Skin_3&streamName=schick… ✉
An entity reference was found in the document, but there is no reference by that name defined. Often this is caused by misspelling the reference name, unencoded ampersands, or by leaving off the trailing semicolon (;). The most common cause of this error is unencoded ampersands in URLs as described by the WDG in "Ampersands in URLs".
Entity references start with an ampersand (&) and end with a semicolon (;). If you want to use a literal ampersand in your document you must encode it as "&" (even inside URLs!). Be careful to end entity references with a semicolon or your entity reference may get interpreted in connection with the following text. Also keep in mind that named entity references are case-sensitive; &Aelig; and æ are different characters.
If this error appears in some markup generated by PHP's session handling code, this article has explanations and solutions to your problem.
Note that in most documents, errors related to entity references will trigger up to 5 separate messages from the Validator. Usually these will all disappear when the original problem is fixed.
Line 100, Column 228: general entity "skinName" not defined and no default entity
…','flashvars','&MM_ComponentVersion=1&skinName=Corona_Skin_3&streamName=schick… ✉
This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.
Line 100, Column 236: reference not terminated by REFC delimiter
…vars','&MM_ComponentVersion=1&skinName=Corona_Skin_3&streamName=schick_aber_sc… ✉
If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.
Line 100, Column 236: reference to entity "skinName" for which no system identifier could be generated
…vars','&MM_ComponentVersion=1&skinName=Corona_Skin_3&streamName=schick_aber_sc… ✉
This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.
Line 100, Column 227: entity was defined here
…e','flashvars','&MM_ComponentVersion=1&skinName=Corona_Skin_3&streamName=schic…
Line 100, Column 251: cannot generate system identifier for general entity "streamName"
…onentVersion=1&skinName=Corona_Skin_3&streamName=schick_aber_schaedlich&autoPl… ✉
An entity reference was found in the document, but there is no reference by that name defined. Often this is caused by misspelling the reference name, unencoded ampersands, or by leaving off the trailing semicolon (;). The most common cause of this error is unencoded ampersands in URLs as described by the WDG in "Ampersands in URLs".
Entity references start with an ampersand (&) and end with a semicolon (;). If you want to use a literal ampersand in your document you must encode it as "&" (even inside URLs!). Be careful to end entity references with a semicolon or your entity reference may get interpreted in connection with the following text. Also keep in mind that named entity references are case-sensitive; &Aelig; and æ are different characters.
If this error appears in some markup generated by PHP's session handling code, this article has explanations and solutions to your problem.
Note that in most documents, errors related to entity references will trigger up to 5 separate messages from the Validator. Usually these will all disappear when the original problem is fixed.
Line 100, Column 251: general entity "streamName" not defined and no default entity
…onentVersion=1&skinName=Corona_Skin_3&streamName=schick_aber_schaedlich&autoPl… ✉
This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.
Line 100, Column 261: reference not terminated by REFC delimiter
…on=1&skinName=Corona_Skin_3&streamName=schick_aber_schaedlich&autoPlay=false&a… ✉
If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.
Line 100, Column 261: reference to entity "streamName" for which no system identifier could be generated
…on=1&skinName=Corona_Skin_3&streamName=schick_aber_schaedlich&autoPlay=false&a… ✉
This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.
Line 100, Column 250: entity was defined here
…ponentVersion=1&skinName=Corona_Skin_3&streamName=schick_aber_schaedlich&autoP…
Line 100, Column 285: cannot generate system identifier for general entity "autoPlay"
…n_3&streamName=schick_aber_schaedlich&autoPlay=false&autoRewind=false','qualit… ✉
An entity reference was found in the document, but there is no reference by that name defined. Often this is caused by misspelling the reference name, unencoded ampersands, or by leaving off the trailing semicolon (;). The most common cause of this error is unencoded ampersands in URLs as described by the WDG in "Ampersands in URLs".
Entity references start with an ampersand (&) and end with a semicolon (;). If you want to use a literal ampersand in your document you must encode it as "&" (even inside URLs!). Be careful to end entity references with a semicolon or your entity reference may get interpreted in connection with the following text. Also keep in mind that named entity references are case-sensitive; &Aelig; and æ are different characters.
If this error appears in some markup generated by PHP's session handling code, this article has explanations and solutions to your problem.
Note that in most documents, errors related to entity references will trigger up to 5 separate messages from the Validator. Usually these will all disappear when the original problem is fixed.
Line 100, Column 285: general entity "autoPlay" not defined and no default entity
…n_3&streamName=schick_aber_schaedlich&autoPlay=false&autoRewind=false','qualit… ✉
This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.
Line 100, Column 293: reference not terminated by REFC delimiter
…amName=schick_aber_schaedlich&autoPlay=false&autoRewind=false','quality','high… ✉
If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.
Line 100, Column 293: reference to entity "autoPlay" for which no system identifier could be generated
…amName=schick_aber_schaedlich&autoPlay=false&autoRewind=false','quality','high… ✉
This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.
Line 100, Column 284: entity was defined here
…in_3&streamName=schick_aber_schaedlich&autoPlay=false&autoRewind=false','quali…
Line 100, Column 300: cannot generate system identifier for general entity "autoRewind"
…schick_aber_schaedlich&autoPlay=false&autoRewind=false','quality','high','scal… ✉
An entity reference was found in the document, but there is no reference by that name defined. Often this is caused by misspelling the reference name, unencoded ampersands, or by leaving off the trailing semicolon (;). The most common cause of this error is unencoded ampersands in URLs as described by the WDG in "Ampersands in URLs".
Entity references start with an ampersand (&) and end with a semicolon (;). If you want to use a literal ampersand in your document you must encode it as "&" (even inside URLs!). Be careful to end entity references with a semicolon or your entity reference may get interpreted in connection with the following text. Also keep in mind that named entity references are case-sensitive; &Aelig; and æ are different characters.
If this error appears in some markup generated by PHP's session handling code, this article has explanations and solutions to your problem.
Note that in most documents, errors related to entity references will trigger up to 5 separate messages from the Validator. Usually these will all disappear when the original problem is fixed.
Line 100, Column 300: general entity "autoRewind" not defined and no default entity
…schick_aber_schaedlich&autoPlay=false&autoRewind=false','quality','high','scal… ✉
This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.
Line 100, Column 310: reference not terminated by REFC delimiter
…r_schaedlich&autoPlay=false&autoRewind=false','quality','high','scale','noscal… ✉
If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.
Line 100, Column 310: reference to entity "autoRewind" for which no system identifier could be generated
…r_schaedlich&autoPlay=false&autoRewind=false','quality','high','scale','noscal… ✉
This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.
Line 100, Column 299: entity was defined here
…=schick_aber_schaedlich&autoPlay=false&autoRewind=false','quality','high','sca…
Line 108, Column 60: reference not terminated by REFC delimiter
…FlashVars" value="&MM_ComponentVersion=1&skinName=Corona_Skin_3&streamName=sch… ✉
If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.
Line 108, Column 60: reference to external entity in attribute value
…FlashVars" value="&MM_ComponentVersion=1&skinName=Corona_Skin_3&streamName=sch… ✉
This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&'.
Line 108, Column 60: reference to entity "MM_ComponentVersion" for which no system identifier could be generated
…FlashVars" value="&MM_ComponentVersion=1&skinName=Corona_Skin_3&streamName=sch… ✉
This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.
Line 100, Column 205: entity was defined here
…,'FLVPlayer_Progressive','flashvars','&MM_ComponentVersion=1&skinName=Corona_S…
Line 108, Column 71: reference not terminated by REFC delimiter
…value="&MM_ComponentVersion=1&skinName=Corona_Skin_3&streamName=schick_aber_sc… ✉
If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.
Line 108, Column 71: reference to external entity in attribute value
…value="&MM_ComponentVersion=1&skinName=Corona_Skin_3&streamName=schick_aber_sc… ✉
This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&'.
Line 108, Column 71: reference to entity "skinName" for which no system identifier could be generated
…value="&MM_ComponentVersion=1&skinName=Corona_Skin_3&streamName=schick_aber_sc… ✉
This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.
Line 100, Column 227: entity was defined here
…e','flashvars','&MM_ComponentVersion=1&skinName=Corona_Skin_3&streamName=schic…
Line 108, Column 96: reference not terminated by REFC delimiter
…on=1&skinName=Corona_Skin_3&streamName=schick_aber_schaedlich&autoPlay=false&a… ✉
If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.
Line 108, Column 96: reference to external entity in attribute value
…on=1&skinName=Corona_Skin_3&streamName=schick_aber_schaedlich&autoPlay=false&a… ✉
This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&'.
Line 108, Column 96: reference to entity "streamName" for which no system identifier could be generated
…on=1&skinName=Corona_Skin_3&streamName=schick_aber_schaedlich&autoPlay=false&a… ✉
This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.
Line 100, Column 250: entity was defined here
…ponentVersion=1&skinName=Corona_Skin_3&streamName=schick_aber_schaedlich&autoP…
Line 108, Column 128: reference not terminated by REFC delimiter
…na_Skin_3&streamName=schick_aber_schaedlich&autoPlay=false&autoRewind=false" /> ✉
If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.
Line 108, Column 128: reference to external entity in attribute value
…na_Skin_3&streamName=schick_aber_schaedlich&autoPlay=false&autoRewind=false" /> ✉
This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&'.
Line 108, Column 128: reference to entity "autoPlay" for which no system identifier could be generated
…na_Skin_3&streamName=schick_aber_schaedlich&autoPlay=false&autoRewind=false" /> ✉
This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.
Line 100, Column 284: entity was defined here
…in_3&streamName=schick_aber_schaedlich&autoPlay=false&autoRewind=false','quali…
Line 108, Column 145: reference not terminated by REFC delimiter
…na_Skin_3&streamName=schick_aber_schaedlich&autoPlay=false&autoRewind=false" /> ✉
If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.
Line 108, Column 145: reference to external entity in attribute value
…na_Skin_3&streamName=schick_aber_schaedlich&autoPlay=false&autoRewind=false" /> ✉
This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&'.
Line 108, Column 145: reference to entity "autoRewind" for which no system identifier could be generated
…na_Skin_3&streamName=schick_aber_schaedlich&autoPlay=false&autoRewind=false" /> ✉
This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.
Line 100, Column 299: entity was defined here
…=schick_aber_schaedlich&autoPlay=false&autoRewind=false','quality','high','sca…
Line 109, Column 20: there is no attribute "src"
"FLVPlayer_Progressive.swf" flashvars="&MM_ComponentVersion=… ✉
You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).
This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.
How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the element to incorporate flash media in a Web page, see the FAQ item on valid flash.
Line 109, Column 58: there is no attribute "flashvars"
…"FLVPlayer_Progressive.swf" flashvars="&MM_ComponentVersion=1&skinName=Corona_… ✉
You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).
This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.
How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the element to incorporate flash media in a Web page, see the FAQ item on valid flash.
Line 109, Column 79: reference not terminated by REFC delimiter
…e.swf" flashvars="&MM_ComponentVersion=1&skinName=Corona_Skin_3&streamName=sch… ✉
If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.
Line 109, Column 79: reference to external entity in attribute value
…e.swf" flashvars="&MM_ComponentVersion=1&skinName=Corona_Skin_3&streamName=sch… ✉
This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&'.
Line 109, Column 79: reference to entity "MM_ComponentVersion" for which no system identifier could be generated
…e.swf" flashvars="&MM_ComponentVersion=1&skinName=Corona_Skin_3&streamName=sch… ✉
This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.
Line 100, Column 205: entity was defined here
…,'FLVPlayer_Progressive','flashvars','&MM_ComponentVersion=1&skinName=Corona_S…
Line 109, Column 90: reference not terminated by REFC delimiter
…hvars="&MM_ComponentVersion=1&skinName=Corona_Skin_3&streamName=schick_aber_sc… ✉
If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.
Line 109, Column 90: reference to external entity in attribute value
…hvars="&MM_ComponentVersion=1&skinName=Corona_Skin_3&streamName=schick_aber_sc… ✉
This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&'.
Line 109, Column 90: reference to entity "skinName" for which no system identifier could be generated
…hvars="&MM_ComponentVersion=1&skinName=Corona_Skin_3&streamName=schick_aber_sc… ✉
This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.
Line 100, Column 227: entity was defined here
…e','flashvars','&MM_ComponentVersion=1&skinName=Corona_Skin_3&streamName=schic…
Line 109, Column 115: reference not terminated by REFC delimiter
…on=1&skinName=Corona_Skin_3&streamName=schick_aber_schaedlich&autoPlay=false&a… ✉
If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.
Line 109, Column 115: reference to external entity in attribute value
…on=1&skinName=Corona_Skin_3&streamName=schick_aber_schaedlich&autoPlay=false&a… ✉
This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&'.
Line 109, Column 115: reference to entity "streamName" for which no system identifier could be generated
…on=1&skinName=Corona_Skin_3&streamName=schick_aber_schaedlich&autoPlay=false&a… ✉
This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.
Line 100, Column 250: entity was defined here
…ponentVersion=1&skinName=Corona_Skin_3&streamName=schick_aber_schaedlich&autoP…
Line 109, Column 147: reference not terminated by REFC delimiter
…amName=schick_aber_schaedlich&autoPlay=false&autoRewind=false" quality="high" … ✉
If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.
Line 109, Column 147: reference to external entity in attribute value
…amName=schick_aber_schaedlich&autoPlay=false&autoRewind=false" quality="high" … ✉
This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&'.
Line 109, Column 147: reference to entity "autoPlay" for which no system identifier could be generated
…amName=schick_aber_schaedlich&autoPlay=false&autoRewind=false" quality="high" … ✉
This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.
Line 100, Column 284: entity was defined here
…in_3&streamName=schick_aber_schaedlich&autoPlay=false&autoRewind=false','quali…
Line 109, Column 164: reference not terminated by REFC delimiter
…r_schaedlich&autoPlay=false&autoRewind=false" quality="high" scale="noscale" w… ✉
If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.
Line 109, Column 164: reference to external entity in attribute value
…r_schaedlich&autoPlay=false&autoRewind=false" quality="high" scale="noscale" w… ✉
This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&'.
Line 109, Column 164: reference to entity "autoRewind" for which no system identifier could be generated
…r_schaedlich&autoPlay=false&autoRewind=false" quality="high" scale="noscale" w… ✉
This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.
Line 100, Column 299: entity was defined here
…=schick_aber_schaedlich&autoPlay=false&autoRewind=false','quality','high','sca…
Line 109, Column 180: there is no attribute "quality"
…oPlay=false&autoRewind=false" quality="high" scale="noscale" width="448" heigh… ✉
You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).
This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.
How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the element to incorporate flash media in a Web page, see the FAQ item on valid flash.
Line 109, Column 193: there is no attribute "scale"
…utoRewind=false" quality="high" scale="noscale" width="448" height="256" name=… ✉
You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).
This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.
How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the element to incorporate flash media in a Web page, see the FAQ item on valid flash.
Line 109, Column 209: there is no attribute "width"
… quality="high" scale="noscale" width="448" height="256" name="FLVPlayer" sali… ✉
You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).
This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.
How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the element to incorporate flash media in a Web page, see the FAQ item on valid flash.
Line 109, Column 222: there is no attribute "height"
…h" scale="noscale" width="448" height="256" name="FLVPlayer" salign="LT" type=… ✉
You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).
This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.
How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the element to incorporate flash media in a Web page, see the FAQ item on valid flash.
Line 109, Column 233: there is no attribute "name"
…oscale" width="448" height="256" name="FLVPlayer" salign="LT" type="applicatio… ✉
You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).
This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.
How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the element to incorporate flash media in a Web page, see the FAQ item on valid flash.
Line 109, Column 252: there is no attribute "salign"
… height="256" name="FLVPlayer" salign="LT" type="application/x-shockwave-flash… ✉
You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).
This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.
How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the element to incorporate flash media in a Web page, see the FAQ item on valid flash.
Line 109, Column 262: there is no attribute "type"
…56" name="FLVPlayer" salign="LT" type="application/x-shockwave-flash" pluginsp… ✉
You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).
This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.
How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the element to incorporate flash media in a Web page, see the FAQ item on valid flash.
Line 109, Column 306: there is no attribute "pluginspage"
…cation/x-shockwave-flash" pluginspage="http://www.adobe.com/shockwave/download… ✉
You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).
This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.
How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the element to incorporate flash media in a Web page, see the FAQ item on valid flash.
Line 109, Column 393: element "embed" undefined
…be.com/shockwave/download/download.cgi?P1_Prod_Version=ShockwaveFlash" /> ✉
You have used the element named above in your document, but the document type you are using does not define an element of that name. This error is often caused by:
- incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "" element),
- by using vendor proprietary extensions such as "
  " or "
  " (this is usually fixed by using CSS to achieve the desired effect instead).
  by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  HTML-Code:
  
  "http://www.w3.org/1999/xhtml"> </span>Roggastail Fairwear Fashion aus Berlin - Textilien<span style="color:#000080"> "text/html; charset=utf-8" /> "robots" content="index,follow" /> "de-DE" /> "description" content="Fairplay und Fairness in der Bekleidungsindustrie—reine Utopie wenn wir uns nicht ändern" /> "keywords" content="Bekleidungsindustrie, Textilindustrie,unethische Arbeitspraktiken, Sklaverei, siegel, fairplay, fairness, earth postive, fair wear, gots, fairer handel, fashion, green fashion, schick aber schädlich" /> "../SpryAssets/SpryMenuBarHorizontal.css" rel="stylesheet" type="text/css" /> "../global.css/container.css" rel="stylesheet" type="text/css" /> "../SpryAssets/SpryAccordion.css" rel="stylesheet" type="text/css" /> "shortcut icon" href="../roggastail_favicon.ico" type="image/x-icon" /> "MM_CheckFlashVersion('7,0,0,0','Für den Inhalt dieser Seite ist eine neuere Version von Adobe Flash Player erforderlich. Möchten Sie sie jetzt herunterladen?');"> "container"> "header"> Roggastail Green Fashion aus Berlin "navigation"> "MenuBar1" class="MenuBarHorizontal"> "../index.html">start "../aktuelles/aktuelles.html">aktuelles "fairness.html">fairness "../Galerie/fashion-motive.html" class="MenuBarItemSubmenu">galerie "../Galerie/fashion-motive.html">Motive "../Galerie/fashion-textilien.html">Textilien "../kaufen/fashion-shop.html">kaufen "../Kooperation/index.html">kooperation "../Freunde/index.html">freunde "../Kontakt/index.html">kontakt "../Impressum/index.html">impressum "clearfloat" /> "maincontent"> Fair Play — Für mich nicht nur eine Worthülse "center">Fairness in allen Schritten der Textilentstehung halte ich für den einzig richtigen Weg. Die Bekleidungsindustrie ist für die unethischsten Arbeitspraktiken in der Welt mitverantwortlich. Hierzu zählen Kinderarbeit, Sklaverei, überzogene Arbeitszeiten, sowie unsichere und unhygienische Arbeitsbedingungen. Viele große bekannte Markenunternehmen sind hier ganz vorn dabei. Einen interessanten Artikel zu diesem Thema schrieb "http://www.zeit.de/2012/13/Indien-Textilfabrik-Arbeitsbedingungen">Michael Höft für Die Zeit am 27.03.2012. Die "http://de.sevenload.com/videos/xNzrkFZ-Schick-aber-Schaedlich-Kleidung-die-krank-macht">Dokumentation "Schick aber schädlich" von Inge Altmeier und Reinhard Hornung ( ausgestrahlt auf Arte am 27.07.2007) beleuchtet den Einsatz bedenklicher Chemikalien in der Herstellung und ihre Gefahr für die Arbeiter und Verbraucher. "filmschnipsel"> "center">Wissenswertes zu den T Shirts, Hoodies und Beuteln, sowie Druckfarben "Accordion1" class="Accordion"> "AccordionPanel"> "AccordionPanelTab">Earth Positive "AccordionPanelContent"> "Bilder_Fairness/EarthPositive Logo.jpg" alt="Earth Positive Logo" width="287" height="248" /> "http://www.continentalclothing.com/page/about_earthpositive_apparel">EarthPositive"RegisteredZeichen">® Apparel von Continental Clothing ist 100% biologisch und 90% CO2-reduziert. Erforscht und entwickelt von Continental Clothing Company demonstriert Earth Positive"RegisteredZeichen">® höchstmögliche Standards in einem der weltweit umwelt- und gesundheitsschädlichsten Industriezweige. EarthPositive ergreift direkte Maßnahmen in Bezug auf Umwelt-, soziale und ethische Fragen. Earth Positive Apparel hält die Standards der folgenden Organisationen. "AccordionPanel"> "AccordionPanelTab">Fair Wear Foundation (FWF) "AccordionPanelContent"> Die "http://www.fairwear.org/">Fairwear Foundation (FWF) fördert weltweit faire Arbeitsbedingungen in der Bekleidungsindustrie. Unternehmen, die Mitglied in der FWF werden und den Verhaltenskodex unterzeichnen,verpflichten sich somit zur Einhaltung der Arbeitsrichtlinien in ihren Betrieben. Darüber hinaus verpflichten sie sich alles dafür zu tun, dass alle Unternehmen innerhalb der Lieferkette diese Arbeitsbedingungen respektieren. Der Verhaltenskondex: keine Kinderarbeit; keine Zwangsarbeit; sichere und gesunde Arbeitsbedingungen; gültige Arbeitsverträge; Zahlung von existenzsichernden Mindestlöhnen; Vereinigungsfreiheit und das Recht auf Kollektivverhandlungen; keine Diskriminierung von Beschäftigten; keine exzessiven Arbeitszeiten "AccordionPanel"> "AccordionPanelTab">Global Organic Textil Standard ( GOTS) "AccordionPanelContent"> Die Internationale Arbeitsgruppe zum "http://www.global-standard.org/">Global Organic Textile Standard setzt sich aus vier renommierten Mitgliedsorganisationen zusammen. Der OTA (USA), IVN (Deutschland), Soil Association (UK) und JOCA (Japan). Unter dem Global Organic Textil Standard (GOTS) werden Bauern und Feldarbeiter geschützt - durch strenge soziale Kriterien und durch das Nutzungsverbot giftiger Chemikalien, die die Gesundheit der Bauern und ihrer Familien schwer beeinträchtigen können. "AccordionPanel"> "AccordionPanelTab">Kohlenstoff- Fußabdruck "AccordionPanelContent"> Kohlenstoffarme Produkte Earth Positive(R) Bekleidung wird aus einflussarmer Biobaumwolle in Fabriken hergestellt, die durch erneuerbare Energien betrieben werden. Der Kohlenstoff-Fußabdruck der EP-Produkte wurde um ca 90% reduziert und diese Kalkulation vom "http://www.carbon-label.com/">Carbon Trust zertifiziert. "AccordionPanel"> "AccordionPanelTab">OekoTex 100 Standard "AccordionPanelContent"> Bis zur Einführung des "http://www.oeko-tex.com/OekoTex100_PUBLIC/index_portal.asp?cls=01">Oeko-Tex® Standards 100 gab es weder für Verbraucher ein verlässliches Produktlabel zur Beurteilung der humanökologischen Qualität von Textilien, noch existierte ein einheitlicher Sicherheitsmaßstab für die Unternehmen der Textil- und Bekleidungsindustrie, welcher eine praxisrelevante Bewertung von möglichen Schadstoffen in Textilprodukten ermöglichte. Deshalb haben das Österreichische Textil-Forschungsinstitut (ÖTI) und das deutsche Forschungsinstitut Hohenstein auf der Grundlage ihrer damals bereits bestehenden Prüfnormen gemeinschaftlich den Oeko-Tex® Standard 100 entwickelt.
  Anfänger: Bildtausch mit Animated Gifs: Firefox-Problem
  
  fitho — Sun, 06 May 2012 19:34:09 GMT
  
  Hallo,
  ich habe in ein Spry-Accordion die Thumbs für eine Bildergalerie gepackt, bei Klick wird ein Bild (rauschen.gif) gegen das entsprechende Animated Gif getauscht. Im Safari funktioniert alles einwandfrei, im Firefox läuft nur das Ani-Gif, das zuerst ausgewählt wurde. Erst nach neuem Laden der Seite kann man ein anderes Gif abspielen. Andere Animated Gifs, die sich auf der Seite befinden, laufen problemlos. Ich habe Firefox neu installiert, der Cache ist gelöscht. Kann das am Accordion liegen? Oder sollte man Animated Gifs nicht tauschen? Ich würde mich sehr über einen Tipp freuen. Danke!
  
  HTML-Code:
  
  "box" id="screen"> "bilder/rauschen.gif" alt="Bildrauschen" name="rauschen" width="449" height="300" id="rauschen" onClick="MM_swapImage('rauschen','','bilder/rauschen.gif',1)"> "box col4"> "bilder/grafik/inputsource.gif" width="399" height="28" alt="Bitte auswählen"> "Accordion1" class="Accordion" tabindex="0"> "AccordionPanel"> "AccordionPanelTab illu">Illu / Logo "AccordionPanelContent">"bilder/illus/illu_start_unten.jpg" width="399" height="134"> "AccordionPanel"> "AccordionPanelTab"> Beispiele "AccordionPanelContent"> "bilder/illus/th_businessillu.jpg" alt="Business-Illustrationen" width="99" height="66" onClick="MM_swapImage('rauschen','','bilder/illus/businessillu.gif',1)" onDblClick="MM_swapImgRestore()"> "bilder/illus/th_trisecur3.gif" alt="Trisecur-Illustrationen" width="99" height="66" onClick="MM_swapImage('rauschen','','bilder/illus/trisecur3.gif',1)" onDblClick="MM_swapImgRestore()"> "bilder/illus/th_turnlogo.gif" alt="Logos" width="99" height="66" onClick="MM_swapImage('rauschen','','bilder/illus/logos.gif',1)" onDblClick="MM_swapImgRestore()"> "bilder/illus/th_sonstigeillus.gif" alt="Verschiedene Illustrationen" width="98 " height="66" onClick="MM_swapImage('rauschen','','bilder/illus/sonstigeillus.gif',1)" onDblClick="MM_swapImgRestore()"> "bilder/illus/th_mode.gif" alt="Modestudien" width="99" height="66" onClick="MM_swapImage('rauschen','','bilder/illus/modestudien.gif',1)" onDblClick="MM_swapImgRestore()"> "bilder/illus/th_layout_people.gif" alt="Layout-Illus People" width="99" height="66" onClick="MM_swapImage('rauschen','','bilder/illus/layout_people.gif',1)" onDblClick="MM_swapImgRestore()"> "bilder/illus/th_layout.gif" alt="Layout-Illustrationen" width="99" height="66" onClick="MM_swapImage('rauschen','','bilder/illus/layout.gif',1)" onDblClick="MM_swapImgRestore()"> "bilder/stop.gif" alt="Stop" width="48" height="66" onClick="MM_swapImage('rauschen','','bilder/rauschen.gif',1)">
  
  Spry Framework: Ein- und Ausblendzeit in SpyMenüBar ändern
  
  le4711 — Sun, 06 May 2012 19:04:55 GMT
  
  Hi an alle,
  
  ich habe eine vertikale Navi mit Spry eingebaut und will jetzt die Ausblendzeit der Subnavi auf 0 setzen.
  Ich habe zwar in der .js eine Variable var opentime, closetime ; in Zeile 339 gefunden, kann aber damit nicht wirklich was anfangen.
  Hauptsächlich geht es mir um die Zeit die vergeht, bis die Subnavi wieder ausgeblendet wird. Dies sollte sofort verschwinden, wenn die Maus aus dem Hovergebiet des
  Tags heraus ist und nicht noch ca. eine halbe Sek. sichtbar sein.
  
  Grüße LE4711
  
  MAIL trägt keinen Absendernamen ein
  
  Ugenmeister — Sun, 06 May 2012 17:44:00 GMT
  
  Hallo...
  
  Ich versende von meiner Website per MAIL Emails, was auch funktioniert. Das Problem ist nur dass beim Empfänger (z.B. in Outlook) zwar die Absender-Emailadresse eingetragen wird, jedoch nicht der Absendername. Das heißt in der Emailnachricht selbst wird der Absendername angezeigt (im Beispiel OUTLOOK), jedoch nicht in der Liste mit den eingegangenen Emails.
  
  Im Netz hab ich nichts gefunden, daraum bitte ich HIER um den ein oder anderen Hinweis.
  
  Hier der Code:
  
  PHP-Code:
  
  $empfaenger = $_POST['emailadresse']; $betreff = "Blablabla"; $from = "From: Absendername "; $text = "Blablabla" mail($empfaenger, $betreff, $text, "MIME-Version: 1.0\nContent-type: text/plain; charset=utf-8\r\nContent-Transfer-Encoding: 8bit\n".$from);
  
  Vielen Dank !
  
  Gruss
  UWE
  
  Creative Suite 6 - Steigt Ihr um?
  
  paul_le — Sun, 06 May 2012 13:24:20 GMT
  
  Die Creative Suite 6 steht vor der Türe. Ist die neue Version für Euch interessant, steigt ihr um oder bleibt Ihr bei Eurer aktuellen Version?
  
  Welche der neuen Features gefallen Euch, was fehlt Euch?
  
  http://tv.adobe.com/search/?q=cs6&pr...ase_id=&t_lid=

Adobe Usergroup dreamworker.de

Dreamweaver CS6 Bedienfeldgruppen per Doppelklick schließen - geht nicht mehr (nur bei mir?)

Dreamweaver CS5 Ärger mit PHP

Technologie Weitreichende Neuerungen für interaktive Web-Anwendungen mit Adobe ColdFusion 10

Anfänger: Frage zum Navigationsmenü

Adobe rudert zurück und behebt Lücken in Creative Suite 5.x

Veranstaltung Captivate eSeminare Wochen

Technologie Adobe Muse ab sofort erhältlich

Technologie Adobe Creative Cloud ab sofort verfügbar

Dynamisch: Dateisystem visualisieren mit Tool?

DW Spry Tabbed Panel

W3C Validator Probleme nach Flash Movie Einbindung mit CS3

Roggastail Green Fashion aus Berlin

Fair Play — Für mich nicht nur eine Worthülse

"center">Wissenswertes zu den T Shirts, Hoodies und Beuteln, sowie Druckfarben

Anfänger: Bildtausch mit Animated Gifs: Firefox-Problem

Illu / Logo

Beispiele

Spry Framework: Ein- und Ausblendzeit in SpyMenüBar ändern

MAIL trägt keinen Absendernamen ein

Creative Suite 6 - Steigt Ihr um?

Roggastail

Green Fashion aus Berlin