Hacked By CyberRooT -

SanalYargic | CYBER-Raider.CoM

Warning: mkdir() [function.mkdir]: Permission denied in /home/yourdomain/public_html/t3lib/class.t3lib_div.php on line 2522  Warning: fopen(/home/yourdomain/public_html/uploads/tx_partner/index.html) [function.fopen]: failed to open stream: No such file or directory in /home/yourdomain/public_html/t3lib/class.t3lib_div.php on line 2438  Warning: Cannot modify header information - headers already sent by (output started at /home/yourdomain/public_html/t3lib/class.t3lib_div.php:2522) in /home/yourdomain/public_html/typo3/mod/tools/em/class.em_index.php on line 1939

Ever get beautiful error messages like these ones?

Check the properties of your folders - it is likely they are not write enabled.

In my travels today, I happened across a great tutorial addressing the technical aspects of “on-page” search engine optimisation.

My complements to Dawson Interactive on this and a great range of other articles addressing Typo3 and Wordpress. You go on my list of community links

I have done some of simpleology’s courses, and they have a new one about blogging .. but I have to link to it to do it. So here goes the automatic link text…

If you are running tt_news and you want to generate an RSS feed from your content, the simplest one to use is incorporated into tt_news itself - but the manual is hard to understand.

For step-by-step instructions, try WEC’s “Set up an RSS fee for your news” tutorial.

NOTE TO SELF:

Don’t forget to check the path in the html.

It must start with a “/” - don’t hardcode, don’t “/../”.

Many people have said that they have found TIMTAB to be a little complex to set up. I think the most complex thing is that it incorporates a couple of extensions, and it has to be done just right.

1. tt_news and ve_guestbook (or other commenting system) need to be installed before TIMTAB
2. It is not essential to use Kubrik, and that can be excluded from “include static from extensions” if you don’t want to use it

After installing TIMTAB, and following the instructions regarding including two instances of the guestbook plugin, I got a little lost because the next instruction was assuming you knew what to do with tt_news, and it is a while since I played with that … so I have forgotten it.

Back after a hiatus … to Templavoila 1.2.0 & T3 4.0.4, and errors!

I can’t remember what I was up to when I last posted (funny that … I mean, it’s only 10 months ago!! :S) But I think what happened was that I thought I would try to create an offline installation to play with, and then discovered that I was operating in different versions of both TV and T3, then got very busy with life, and Christmas, and then my two new daughters … and so just didn’t come up with a solution.

So .. now I am back and the first thing that happens is I lose my front end content … grrr. While searching for a solution, I found my own site , and the language localisation solution that I found last year. So I went into the Data Structure XML to have a look and
check the XML was in the right format for language localisation.

I saved the XML, and then came up with this error.

(Then I found the solution to my first problem on Dmitry’s blog … only I had
already made this error happen )

My DS is there in list view and in TV view. I don’t get options to edit
header info or mapping with the tabs… I just get…

TemplaVoilà
Template Mapping

Template Object Information:
Template Object Details:
Template Object:     templatename[Template]
Template File:     fileadmin/templates/foldername/filename.htm
Data Structure Record:     DSrecordname

Error: No Data Structure Record could be found with UID “14″

And yet … I could find it in list

Oh well … just wouldn’t be Typo3 without *something* to confuse me

I did forget a couple of things.

One is, even after selecting the starting point for the plugin, and pid’s to ignore, it didn’t do those things. I actually had to put the sysfolder with the queries into the branch of the website that the queries were for.

The other thing I forgot to say is that the stylesheet for the plugin rendering is actually in the same file as the template.

No, too involved, can’t be bothered. I am back to setting it up with TS template.

So .. I have gotten it to work.

First of all, a little explanation.

The tx_gstselectpro extension *can* be used as a flexible content element with templavoila - but only if it is the only instance in your whole site.

Otherwise it is better to call each instance as a lib.myObject, in order to configure it more accurately.

My typoscript looks like this (taken from the file gst_selectpro-1.0.0-ext_typoscript_setup__txt which is included in the extension download):

#latest artlicles teasers
lib.latestarticles < plugin.tx_gstselectpro_pi1
lib.latestarticles = USER
lib.latestarticles {

    // Set the administration parameters.
    debugSQL = {$plugin.gstselectpro.debugSQL}

    // Set the administration parameters.
    useResForTempl = {$plugin.gstselectpro.useResForTempl}
    useParseFunc = {$plugin.gstselectpro.useParseFunc}
    useStripTags = {$plugin.gstselectpro.useStripTags}
    unsetLastSeparator = {$plugin.gstselectpro.unsetLastSeparator}
    useContUid = {$plugin.gstselectpro.useContUid}

    // Set the query parameters.
    queryPid = 1121

    // Set the imgage directories parameters.
   directories {
          path = {$plugin.gstselectpro.directories.path}
          all = {$plugin.gstselectpro.directories.all}
    } // end directories

    // Set the css parameters.
    classTdBrowse = {$plugin.gstselectpro.classTdBrowse}

    // Set the parseFunc parameters.
    text_parseFunc {
    } // end text_parseFunc

    // Set the standard wrap parameters.
    text_stdWrap {
    } // end text_stdWrap

    image_stdWrap {
    } // end image_stdWrap

    date_stdWrap {
    } // end date_stdWrap

    link_stdWrap {
    } // end link_stdWrap

/* -disabled by default-
    // Change local language variables.

    _LOCAL_LANG.default.dateFormat = %A, %m-%d-%Y
    _LOCAL_LANG.de.dateFormat = %A, %d.%m.%Y
    _LOCAL_LANG.fr.dateFormat = %A, %d/%m/%Y

*/

}
NOTE: that I set the queryPid exactly for this lib.myObject, rather than leaving it as queryPid = {$plugin.gstselectpro.queryPid}My constants are exactly the same as the sample constants file, gst_selectpro-1.0.0-ext_typoscript_constants__txt. My constants are exactly the same as the sample constants file,Now, while it is possible to use the extension with TV, it is still necessary to create a template file containing the markers used by the extension for the data to render correctly.The extension includes three sample templates to give you an idea how to do it.