PROBLEM: The DAM extension ver. 1.0.14 showed a bug installed in Typo3 4.2.3: on the Media->File module, whenever the table on the right frame was used for navigation purposes and a directory was clicked to access its content, a 404 error was issued stating that the directory did not exist.
SOLUTION: The problem was related to the fact that the SLCMD GET-variable contained an absolute path instead of a relative one (relative to the root of the website I mean). The solution consisted in correcting the path before wrapping the directory links with it. Therefore the file class.tx_dam_listbase.php has been modified: at the beginning of the function linkWrapDir (at line 874) the follwing lines of code have been inserted:
if(t3lib_div::_GET('SLCMD')) {
$old_slcmd = t3lib_div::_GET('SLCMD');
$new_slcmd = $old_slcmd;
if ($old_slcmd['SELECT']['txdamFolder']) {
$abs_path = key($old_slcmd['SELECT']['txdamFolder']);
$rel_path = tx_dam::file_relativeSitePath($abs_path);
$rel_arr = array($rel_path => 1);
$new_slcmd['SELECT']['txdamFolder'] = $rel_arr;
}
t3lib_div::_GETset($new_slcmd,'SLCMD');
}
Friday, December 19, 2008
Thursday, December 18, 2008
TYPO3 Fatal Error: Extension key "sv" was NOT loaded! (t3lib_extMgm::extPath)
Suddenly, we received this error message under /typo3 BE interface:
TYPO3 Fatal Error: Extension key "sv" was NOT loaded! (t3lib_extMgm::extPath)
The web site was not reachable with similar error:
TYPO3 Fatal Error: Extension key "cms" was NOT loaded! (t3lib_extMgm::extPath)
Just delete all files "temp_.......php" in the /typo3conf directory and the site will work again.
TYPO3 Fatal Error: Extension key "sv" was NOT loaded! (t3lib_extMgm::extPath)
The web site was not reachable with similar error:
TYPO3 Fatal Error: Extension key "cms" was NOT loaded! (t3lib_extMgm::extPath)
Just delete all files "temp_.......php" in the /typo3conf directory and the site will work again.
Monday, December 15, 2008
RTE creation of hyperlink bug
In the RTE in some installation of typo3, the wizard to create a link does not work.
We modified the extension HtmlArea:
1. open \typo3\sysext\rtehtmlarea\mod3\class.tx_rtehtmlarea_browse_links.php
add this code at the line 356:
if ($this->editorNo=='')
$this->editorNo = 1;
We modified the extension HtmlArea:
1. open \typo3\sysext\rtehtmlarea\mod3\class.tx_rtehtmlarea_browse_links.php
add this code at the line 356:
if ($this->editorNo=='')
$this->editorNo = 1;
Frontend editing
In order to see in FE side the pencil to modify the content in frontend, it is required to insert in the TSconfig field of the usergroup record the following lines:
admPanel {
enable.edit = 1
module.edit.forceDisplayFieldIcons = 1
hide = 1
}
admPanel {
enable.edit = 1
module.edit.forceDisplayFieldIcons = 1
hide = 1
}
Login backend and frontend
To Insert a dropdown menu in hte login page to select the interface (backend or frontend) go into install menu and insert on [interfaces] section "frontend,backend"
DAM Detail page
The detail view for the DAM resources uses PHP-include as an external procedure to get the data from the database and "smarty library" that allows to keep separated the code from the template. The smarty version used in typo3 is 1.2.6, this extension has been released by Simon Tuck on 19.03.2008
On the detail page you can see the data referred to the DAM and if there is a picture, will be created a thumbnail and resized to 100px.
URL: http://typo3dev.bioversity.cgiar.org/records/dam_asset_detail.html?tx_dam%5Buid%5D=1&tx_dam%5BbackPid%5D=214&cHash=6911335
On the detail page you can see the data referred to the DAM and if there is a picture, will be created a thumbnail and resized to 100px.
URL: http://typo3dev.bioversity.cgiar.org/records/dam_asset_detail.html?tx_dam%5Buid%5D=1&tx_dam%5BbackPid%5D=214&cHash=6911335
Mailer
Under typo3conf/ext/user_bioversity_updatereminder/mail/mailer.php it is possible to see the reminder
Wednesday, December 10, 2008
Move/Rename Search Page
Whenever you want to change name and/or location of the search page please remember to update the 5 occurrences of the search template and the only occurrence in the main template (both in the root page).
Now the search page is called "search", so, for example, if we would like to change it to "search page", we need to change the following lines of the search template:
tt_content.name = <a href="http://www.bioversityinternational.org/search/#sito">Pages</a>
tt_news.name = <a href="http://www.bioversityinternational.org/search/#news">News</a>
user_bioversitypublications_data.name = <a href="http://www.bioversityinternational.org/search/#pubbs">Publications</a>
tx_dam.name = <a href="http://www.bioversityinternational.org/search/#docs">Documents</a>
user_bioversityinfores_data.name = <a href="http://www.bioversityinternational.org/search/#infos">Information Resources</a>
To:
tt_content.name = <a href="http://www.bioversityinternational.org/search_page/#sito">Pages</a>
tt_news.name = <a href="http://www.bioversityinternational.org/search_page/#news">News</a>
user_bioversitypublications_data.name = <a href="http://www.bioversityinternational.org/search_page/#pubbs">Publications</a>
tx_dam.name = <a href="http://www.bioversityinternational.org/search_page/#docs">Documents</a>
user_bioversityinfores_data.name = <a href="http://www.bioversityinternational.org/search_page/#infos">Information Resources</a>
And inside the main template, the following line:
lib.search.value = search/
Must be changed to:
lib.search.value = search_page/
Now the search page is called "search", so, for example, if we would like to change it to "search page", we need to change the following lines of the search template:
tt_content.name = <a href="http://www.bioversityinternational.org/search/#sito">Pages</a>
tt_news.name = <a href="http://www.bioversityinternational.org/search/#news">News</a>
user_bioversitypublications_data.name = <a href="http://www.bioversityinternational.org/search/#pubbs">Publications</a>
tx_dam.name = <a href="http://www.bioversityinternational.org/search/#docs">Documents</a>
user_bioversityinfores_data.name = <a href="http://www.bioversityinternational.org/search/#infos">Information Resources</a>
To:
tt_content.name = <a href="http://www.bioversityinternational.org/search_page/#sito">Pages</a>
tt_news.name = <a href="http://www.bioversityinternational.org/search_page/#news">News</a>
user_bioversitypublications_data.name = <a href="http://www.bioversityinternational.org/search_page/#pubbs">Publications</a>
tx_dam.name = <a href="http://www.bioversityinternational.org/search_page/#docs">Documents</a>
user_bioversityinfores_data.name = <a href="http://www.bioversityinternational.org/search_page/#infos">Information Resources</a>
And inside the main template, the following line:
lib.search.value = search/
Must be changed to:
lib.search.value = search_page/
Friday, December 5, 2008
Order By Wrapping Functionality
PROBLEM: Could not use the wrapping function with the ORDER BY clause, useful for the return of customized order such as ORDER BY FIELD(uid, uid_list);
SOLUTION:
In file : typo3/sysext/cms/tslib/class.tslib_content.php
add at line #6900 (anyway before "if (trim($conf['orderBy......"):
$conf['orderBy'] = trim($this->stdWrap($conf['orderBy'],$conf['orderBy.']));
SOLUTION:
In file : typo3/sysext/cms/tslib/class.tslib_content.php
add at line #6900 (anyway before "if (trim($conf['orderBy......"):
$conf['orderBy'] = trim($this->stdWrap($conf['orderBy'],$conf['orderBy.']));
Thursday, December 4, 2008
RTE Generic Records BUG
PROBLEM: The "RTE Generic Records" extension (ch_rterecords) featured a bug with typo3 4.2.3 when adding a link to the text inside the RTE: many JavaScript errors arose each time the link pop-up window opened. Making it impossible to insert links inside the RTE. The "RTE Generic Records" extension version considered is 1.0.8, HTMLArea 1.77, and Typo3 4.2.3.
SOLUTION: The file class.ux_tx_rtehtmlarea_browse_links.php (inside the "RTE Generic Records") has been modified and rewritten in many parts, since it was not compatible with the new JavaScript functions used within the HTMLArea extension. The structure was kept but prototypes of functions have changed and parts of code were included.
The new customized extension can be downloaded here.
The customized file can be downloaded here at class.ux_tx_rtehtmlarea_browse_links.php
SOLUTION: The file class.ux_tx_rtehtmlarea_browse_links.php (inside the "RTE Generic Records") has been modified and rewritten in many parts, since it was not compatible with the new JavaScript functions used within the HTMLArea extension. The structure was kept but prototypes of functions have changed and parts of code were included.
The new customized extension can be downloaded here.
The customized file can be downloaded here at class.ux_tx_rtehtmlarea_browse_links.php
Labels:
HTMLArea,
RTE,
RTE Generic records
Wednesday, December 3, 2008
Preserve entity characters in typo3 RTE
In order to preserve Character entities in RTE form in typo3, it is required to insert in the homepage TS Config of the site this code:
RTE.default.proc.htmlSpecialChars = 0
RTE.default.proc.htmlSpecialChars.preserveEntities = 0
, &, etc. will not be converted in  , &, etc.
For tt_news the TS Config is:
RTE.config.tt_news.bodytext.proc.htmlSpecialChars = 0
RTE.config.tt_news.bodytext.proc.htmlSpecialChars.preserveEntities = 0
RTE.default.proc.htmlSpecialChars = 0
RTE.default.proc.htmlSpecialChars.preserveEntities = 0
, &, etc. will not be converted in  , &, etc.
For tt_news the TS Config is:
RTE.config.tt_news.bodytext.proc.htmlSpecialChars = 0
RTE.config.tt_news.bodytext.proc.htmlSpecialChars.preserveEntities = 0
Clean MS Word formatting in typo3
Typo3 supports the cleaning of text pasted in the RTE form from a MS Word document.
Directives must be included in the TS Config of the homepage, like:
RTE.default.enableWordClean = 1
RTE.default.enableWordClean.HTMLparser < RTE.default.proc.entryHTMLparser_db
The right procedure to copy and paste text from MS Word file is:
Directives must be included in the TS Config of the homepage, like:
RTE.default.enableWordClean = 1
RTE.default.enableWordClean.HTMLparser < RTE.default.proc.entryHTMLparser_db
The right procedure to copy and paste text from MS Word file is:
- Copy the text from MS Word
- Paste into the Rich Text Editor form of typo3
- Clean the content with the cleaner plugin icon checking "MS Word formatting.
We tried many times and the text is cleaned at 90%/95%; sometimes dirty text remains on the top and can be selected and deleted easily.
Monday, December 1, 2008
Direct Mail extension modified.
The file modified by Antonio is:
/srv/www/htdocs/typo3conf/ext/direct_mail/res/scripts/class.dmailer.php
He modified the function dmailer_masssend_list (line 458) and added the function lookForMetadataONtt_address (line 535).
/srv/www/htdocs/typo3conf/ext/direct_mail/res/scripts/class.dmailer.php
He modified the function dmailer_masssend_list (line 458) and added the function lookForMetadataONtt_address (line 535).
Push2RSS first BUG
This extension featured a strange bug which was corrected immediately. It was in the class.tx_push2rss3ds_tce.php file at line 36. A variable called $this was not legal because it reassigned the reserved variable $this. The variable was renamed to $thiss whenever it occurs in the function, and now it works fine.
Subscribe to:
Posts (Atom)