Line break issues
I don't know if this has been raised yet with CC2008, but I know it has been an issue in previous versions as well (see http://www.coffeecup.com/forums/topic-a … estarter/7).
The problem is that line returns are getting misinterpreted or re-written. eg:
}
// Reload the page in the browser window
becomes:
} // Reload the page in the browser window
or similar.
Any resolution planned? I did not see this with 2007R2...
The problem is that line returns are getting misinterpreted or re-written. eg:
}
// Reload the page in the browser window
becomes:
} // Reload the page in the browser window
or similar.
Any resolution planned? I did not see this with 2007R2...
The discussion you referred to was about Direct FTP. The current beta version does not insert or remove blank lines.
Could you explain a bit more about WHEN in the process this line break issue occurs? When you reopen after saving? After having applied Code Cleaner? After upload/download, and with which FTP application?
Could you explain a bit more about WHEN in the process this line break issue occurs? When you reopen after saving? After having applied Code Cleaner? After upload/download, and with which FTP application?
Ha en riktig god dag!
Inger, Norway
My work in progress:
Components for Site Designer and the HTML Editor: https://mock-up.coffeecup.com
Inger, Norway
My work in progress:
Components for Site Designer and the HTML Editor: https://mock-up.coffeecup.com
Here's an example:
I downloaded a zip file from osCommerce (via IE7), extracted it (using WinZip), and opened a php file in CC2008:
*/ require('includes/application_top.php'); if (!tep_session_is_registered('customer_id')) {
$navigation->set_snapshot();
tep_redirect(tep_href_link(FILENAME_LOGIN, '', 'SSL'));
} require(DIR_WS_LANGUAGES . $language . '/' . FILENAME_ACCOUNT); $breadcrumb->add(NAVBAR_TITLE, tep_href_link(FILENAME_ACCOUNT, '', 'SSL')); $content = CONTENT_ACCOUNT;
$javascript = $content . '.js'; require(DIR_WS_TEMPLATES . TEMPLATE_NAME . '/' . TEMPLATENAME_MAIN_PAGE); require(DIR_WS_INCLUDES . 'application_bottom.php');?>
Notice that the line breaks before the two "require" commands, and before the closing php tag are gone? Also, when you try to close the file without editing, CC2008 tells you that the file has changed.
I also opened the file in CC 2007R2:
require('includes/application_top.php');
if (!tep_session_is_registered('customer_id')) {
$navigation->set_snapshot();
tep_redirect(tep_href_link(FILENAME_LOGIN, '', 'SSL'));
}
require(DIR_WS_LANGUAGES . $language . '/' . FILENAME_ACCOUNT);
$breadcrumb->add(NAVBAR_TITLE, tep_href_link(FILENAME_ACCOUNT, '', 'SSL'));
$content = CONTENT_ACCOUNT;
$javascript = $content . '.js';
require(DIR_WS_TEMPLATES . TEMPLATE_NAME . '/' . TEMPLATENAME_MAIN_PAGE);
require(DIR_WS_INCLUDES . 'application_bottom.php');
?>
Linebreaks are all preserved in CC2007.
I chose this file at random for demonstration, but it can be ANY file...
I downloaded a zip file from osCommerce (via IE7), extracted it (using WinZip), and opened a php file in CC2008:
*/ require('includes/application_top.php'); if (!tep_session_is_registered('customer_id')) {
$navigation->set_snapshot();
tep_redirect(tep_href_link(FILENAME_LOGIN, '', 'SSL'));
} require(DIR_WS_LANGUAGES . $language . '/' . FILENAME_ACCOUNT); $breadcrumb->add(NAVBAR_TITLE, tep_href_link(FILENAME_ACCOUNT, '', 'SSL')); $content = CONTENT_ACCOUNT;
$javascript = $content . '.js'; require(DIR_WS_TEMPLATES . TEMPLATE_NAME . '/' . TEMPLATENAME_MAIN_PAGE); require(DIR_WS_INCLUDES . 'application_bottom.php');?>
Notice that the line breaks before the two "require" commands, and before the closing php tag are gone? Also, when you try to close the file without editing, CC2008 tells you that the file has changed.
I also opened the file in CC 2007R2:
require('includes/application_top.php');
if (!tep_session_is_registered('customer_id')) {
$navigation->set_snapshot();
tep_redirect(tep_href_link(FILENAME_LOGIN, '', 'SSL'));
}
require(DIR_WS_LANGUAGES . $language . '/' . FILENAME_ACCOUNT);
$breadcrumb->add(NAVBAR_TITLE, tep_href_link(FILENAME_ACCOUNT, '', 'SSL'));
$content = CONTENT_ACCOUNT;
$javascript = $content . '.js';
require(DIR_WS_TEMPLATES . TEMPLATE_NAME . '/' . TEMPLATENAME_MAIN_PAGE);
require(DIR_WS_INCLUDES . 'application_bottom.php');
?>
Linebreaks are all preserved in CC2007.
I chose this file at random for demonstration, but it can be ANY file...
Inger, Any ideas?
bump?
As far as I know, this issue is still unresolved. Any help please?
Have you sent this issue to CoffeeCup help directly? Maybe the volunteers here in the forum don't know how to fix this one.
http://www.coffeecup.com/help/
log in and send them a support request, and maybe they can help.
http://www.coffeecup.com/help/
log in and send them a support request, and maybe they can help.
E-Learning Specialist
www.mainsites.ca is my website, and yes, some of it is crappy.
www.mainsites.ca is my website, and yes, some of it is crappy.
Line breaks before Comment lines <!-- --> are removed when switching between the visual editor and code editors. So if you have the following:
<p>My paragragh</p>
<!-- Comment 1 -->
<!-- Comment 2 -->
You will end up with:
<p>My paragragh</p><!-- Comment 1 --><!-- Comment 2 -->
I noticed that this does not happen if the comment is after an <hr> tag.
It's real annoying. I've been evaluating editors to purchase for others to contribute edits to our web sites. This bug has me on the fence.
<p>My paragragh</p>
<!-- Comment 1 -->
<!-- Comment 2 -->
You will end up with:
<p>My paragragh</p><!-- Comment 1 --><!-- Comment 2 -->
I noticed that this does not happen if the comment is after an <hr> tag.
It's real annoying. I've been evaluating editors to purchase for others to contribute edits to our web sites. This bug has me on the fence.
FYI, I received a response to my support request on this subject:
"Unfortunately, we don't have an ETA of when this will be fixed. Our developers are working on it and hope to have it corrected in the next release."
"Unfortunately, we don't have an ETA of when this will be fixed. Our developers are working on it and hope to have it corrected in the next release."
Have something to add? We’d love to hear it!
You must have an account to participate. Please Sign In Here, then join the conversation.