editors on subdomain

I've moved my admin into subdomain: http://subdomain.adbc.com
All works fine, but all browser load properly only html_editor, cke and tiny don't work
First moved my admin to subdomain, all works fine.
why this?

100asa:

I've moved my admin into subdomain: http://subdomain.adbc.com
All works fine, but all browser load properly only html_editor, cke and tiny don't work
First moved my admin to subdomain, all works fine.
why this?

Those editors are loaded into the main site area, guessing that the "reference" to them does not incorporate/use the applicable references to their installed location... Not sure why, though, because I know that I have accessed my editors from other areas of my domain (outside of ZC) without issue, though I have programmed hard links to the folders when outside of ZC...

May also help to identify the version of ZC that you are using on which this problem occurs.

I use zencart 1.3.9
Maybe the admin/configure?
or root configure?
but why html editr works fine and tiny-cke don't works?

100asa:

I use zencart 1.3.9
Maybe the admin/configure?
or root configure?
but why html editr works fine and tiny-cke don't works?

Each editor has it's own "call" routine. Would have to look at the code on the page(s) affected to see why one works when another doesn't... For example, I just went into my admin and define page editors using ckeditor. Looking at the page source, I saw that the editor is called relative to the "current" directory rather than an absolute path to the location.

Looking through the files of the site I found that
the admin/includes/ckeditor.php file contains code on line 21 that says:

<script type="text/javascript" src="[how to get to the DIR_WS_EDITORS folder]/<?php echo DIR_WS_EDITORS ?>ckeditor/ckeditor.js"></script>

Where [how to get to the DIR_WS_EDITORS folder] has the relative path information to get from the admin directory to the root directory. Ideally, that portion should reflect the path to where your root directory is, but also take into consideration whether the connection is secure (https) or not secure (http) (assuming that an http/https call is made, although that does not seem to be the way DIR_FS_CATALOG is built/presented). Recommend using proper ZC function calls to build the link, but simply concatenating DIR_FS_CATALOG into the path should address your issue for each instance.

My guess is that the other editors that do not work have a similar statement. Looking at similiar calls in the html_editor.php file the location appears to be built using other ZC variables (DIR_FS_CATALOG for example). (I didn't go and try to find the exact construct for how the html editor is presented).

SOLVED!
Thank you so much: follow your instruction, I've write src="http://www.100asa.it/<?php echo DIR_WS_EDITORS ?>ckeditor/cked......
and now all works fine!

100asa:

SOLVED!
Thank you so much: follow your instruction, I've write src="http://www.100asa.it/<?php echo DIR_WS_EDITORS ?>ckeditor/cked......
and now all works fine!

I would recommend:
src="<?php echo DIR_FS_CATALOG . DIR_WS_EDITORS ?>ckeditor/cked
or if that doesn't work properly (because I apologize I haven't gone back to look at the ending character of DIR_FS_CATALOG) then:
src="<?php echo DIR_FS_CATALOG . '/' . DIR_WS_EDITORS ?>ckeditor/cked

mc12345678:

I would recommend:
src="<?php echo DIR_FS_CATALOG . DIR_WS_EDITORS ?>ckeditor/cked
or if that doesn't work properly (because I apologize I haven't gone back to look at the ending character of DIR_FS_CATALOG) then:
src="<?php echo DIR_FS_CATALOG . '/' . DIR_WS_EDITORS ?>ckeditor/cked

To put it another way, you should avoid hard coding paths and other information as much as possible and use the functions and variables that are a part of ZC. If you were to move your site in the future, you will/would have to recode all of those unique changes instead of simply moving to a new location. Regarding the use of http:// in the beginning of the src statement, you should simply use //. When you are on a secure link (which you should be in your admin area) you will likely receive a statement that you have insecure content on your page, which in fact you do have insecure content that you are typing in. If you use // at the beginning, whatever connection type you are on will be properly handled. But again, you should not hard code your site's address into the path like you have found will work, but is incorrect.