Xinha Discussion Forum

The redirection is set up in the DNS zone, which I do not control. Upon registration I have received these nameservers from Gogo to enter:

Name Server:NS1.HYNERIA.GOGO.CO.NZ
Name Server:NS2.HYNERIA.GOGO.CO.NZ

Which is where the domain is controlled. Making changes there shouldn't be a problem. If you want me to setup different nameservers, please let me know and I'll change them ASAP.

It should be easy to change the zones so that all traffic uses xinha.org instead, instead of the other addresses currently being used, that way people will find it easier to remember the URL.

Never noticed the xinha.org in the release files!

--Rinck

I know this has been discussed before (the whole closures discussion), but are some of these leaks fixable? and what effect would that have on Xinha? Would it also improve loading times in IE? Or just prevent IE from crashing when you reload your page?

you could create such a feature with php or asp, before saving the edited version, compare it with the original version and then for example highlight the changes, although it would be quite an extensive amount of work

It happens in both IE 6.0.2800.1106.xpsp2.050301-1526 as well as in FF version 1.0.1

I thought it might be due to ZoneAlarm Pro at first (since it doesn't allow me to load xinha in IE either, I have to close it first), but even after shutting it down the problem persists...

Should I submit this as a ticket? Can you reproduce this behaviour?

From what I've read so far, I'm kind of in the middle. One the one hand I agree with the fact that the Xinha Core should be completely independent and optimized for useage without any backend system. But on the other hand, many (in my opinion, MOST) project will somehow want to incorporate functionality which is only available on the server side (uploading of files, etc) which means the need for a good integration with backend systems is unmistakably there.

I would personally like to see Xinha being able to work as a standalone application, but also totally plugin ready and being able to provide the necesary information to whatever backend system might arise.

To be honest, aside from the fact that gogo and yermo have different view on some aspects, I don't see why there isn't a solution that satisfies both parties without making any compromises on the actual product itself.

I think from all threads I've read it has become pretty clear that Xinha in its current form is a mess coding-wise, which is mainly an inheritance of InteractiveTools.com, and in order to be able to grow it needs to be (partly) rewritten. Why not take yermo's changes (even though you don't like the coding style, it still does the same thing, yermo already indicated that optimizations are at hand), commit them to the current trunk and work from there? It has been mentioned many times that Xinha needs to be changed in order to better support plugins of ANY type, not just the unified backend.

To cut a long story short, aside from some different perspectives on how things should be done, everyone pretty much wants the same thing, a highly customizable, full featured WYSIWYG editor, so I don't see a valid reason to make another fork and divide your efforts, while working together might be more beneficial and more efficient for all parties involved.

But hey, that's just my opinion and it's late too, so I might change some things tomorrow, and I do really appreciate your efforts yermo, since I personally make use of PHP as well for file uploading and some other custom hacks for my CMS, keep it up!!

New home, www.xinha.org is now officially active...

Foxx

sorry, must have misread your first post, it was late...

Personally I don't use ASP(.NET), but I think there would be plenty that would like to see some great plugins for ASP(.NET), for example a good version of the image/file manager plugin (EFM). I suggest you contact the creator of EFM so maybe you can combine your strenghts. You could make one standard client-side interface and then have two possibilities for server side processing, either ASP or PHP. That way neither of you will be wasting any efforts nor time...

ok, will try and get that fixed as soon as I get home! I also asked you what official email address you'd like to have (currently only as forwarder, no pop boxes yet)... admin@xinha.org?? whatever... lemme know and I'll set it up!

<input type=hidden name=component_id value=[% component.component_id %]>

it is always recommended to put quotes around your attribute values anyways, maybe if you insert them yourself before hand, like so:

<input type="hidden" name="component_id" value="[% component.component_id %]" />

then maybe the problem will be solved!