Xinha Discussion Forum

A 500 error would indicate that your server is causing an error.  Contact your web host for information (or consult the server's error log).  Often times, this can be a server which enforces certain file permissions (no write for group/other) and your file permissions are incorrect (allow write for group/other).

It's a sure bet that your HTML is not valid.

<table><form><tr>

and
 

<table><tr><form><td>

are not valid HTML and produce this problem, <form> can appear outside the <table> or inside the <td> nowhere else.

Without seeing how your plugin works, I can only speak in general terms,

var TranslatedText = Xinha._lc("English Text", 'PluginName');

translates the string "English Text" into the appropriate language, in the "PluginName" scope. 

You put your translations in
/plugins/PluginName/lang/**.js
(where ** is the lang code, "fr" for french etc)

This file must be in UTF-8 encoding (goes for everything).

An example fr.js

// I18N constants
// LANG: "fr", ENCODING: UTF-8
{
  "You must select some text before making a new link.": "Vous devez sélectionner un texte avant de créer un nouveau lien",
  "Are you sure you wish to remove this link?": "Confirmez-vous la suppression de ce lien ?",
  "Remove Link": "Supprimer",
  "URL Link": "Lien URL",
  "Ordinary Link": "Lien standard",
  "Same Window (jump out of frames)": "Même fenêtre (sort des frames)",
  "New Window": "Nouvelle fenêtre",
  "Popup Window": "Fenêtre popup",
  "Email Link": "Lien email",
  "Email Address:": "Adresse email",
  "Subject:": "Sujet",
  "Message Template:": "Message",
  "Size:": "Taille",
  "Name:": "Nom"
};

If you use the "Dialog" system (brief rundown follows) then your dialog html can be like this and the stuff in <l10n> tags and _(....) attributes will be translated automatically.

<label>
  <input type="radio" name="[type]" id="[type_url]" value="url" checked="checked" />
  <l10n>URL Link</l10n>
 </label>

<label for="[href]"><l10n>URL:</l10n> </label>
  <input type="text" name="[href]" id="[href]" style="width:100%" value="http://www.example.com/" />

<input type="button" id="[ok]"     value="_(OK)"     />

Here is a brief rundown on using dialog (see Linker/pluginMethods.js for a complete example) -- note the square brackets are required in ID's, names etc in the HTML, but you omit them in the functions below)

var myDialog = new Xinha.Dialog(theXinhaEditorObject, "html string of your 'dialog'", 'PluginName');
myDialog.show({'fieldName': 'fieldValue, 'anotherField': 'anotherValue'}); // Optional set fields when showing
var fieldValues = myDialog.hide(); // see also myDialog.getValues();

// Additional Useful Functions....
myDialog.toggle();
myDialog.collapse();
myDialog.getElementById('someID');
myDialog.getElementsByName('someName');
myDialog.getElementsByClassName('someClassName');

// See modules/Dialogs/XinhaDialog.js for more

1. Ensure that error reporting is switched on in your php.ini

2. Using Firebug, Chrome Developer Tools, a network sniffer, whatever, examing the request that results in the popup being opened, you need to see that your configuration is being passed from the browser as part of the request.

3. Add some debugging statements to ImageManager/config.inc.php , particularly you should print_r($_REQUEST) to find out what is getting through to the PHP, and you need to find out if xinha_read_passed_data() is returning an appropriate structure (see the conditional).

My next guess is that your unusual server environment is not passing post/get data to PHP correctly.

You'll have to use Firebug to debug it.  Check that it's loading all files for a start.

You won't be able to listen to those things directly, there is no onchange for a start when we are dealing with an iframe (this is how Xinha works).

Look at the plugins CharCounter and SaveOnBlur, and also the code in XinhaCore (somewhere) which connects up the activateEditor handler, I think if you read those things you can probably work out a way to either modify Xinha or better write a plugin which can trigger some callback function to do what you need it to do.

Indicates that an XMLHTTPRequest is failing for some reason.  Possible reasons I can think of....
1. File permissions are incorrect on remote server
2. You are trying to make a cross-domain request (page is on one domain, request is to another)

check config _editor_url is correct

Use your browser's developer tools to inspect a button/s and fiddle with the CSS to find out what you need to change.

Check that your PHP session handling is functional, ensure the session name on both ends (inside your application, and inside the Xinha php components) is the same.

You might also want to look at MootoolsFileManager instead of ExtendedFileManager because the EFM is pretty old.

As would

                   echo "Ending PHP Section. \n";

You would see that occuring if you open the javascript console I expect.

xinha_config.toolbar =
  [
    ["popupeditor"],
    ["separator","formatblock","fontname","fontsize","bold","italic","underline","strikethrough"],
    ["separator","forecolor","hilitecolor","textindicator"],
    ["separator","subscript","superscript"],
    ["linebreak","separator","justifyleft","justifycenter","justifyright","justifyfull"],
    ["separator","insertorderedlist","insertunorderedlist","outdent","indent"],
    ["separator","inserthorizontalrule","createlink","insertimage","inserttable"],
    ["linebreak","separator","undo","redo","selectall","print"], (Xinha.is_gecko ? [] : ["cut","copy","paste","overwrite","saveas"]),
    ["separator","killword","clearfonts","removeformat","toggleborders","splitblock","lefttoright", "righttoleft"],
    ["separator","htmlmode","showhelp","about"]
  ];

??

Exactly like you say, set xinha_config.toolbar ?