Beta 2 Released
Content Type Management
Written by Ercan Özkaya   

Today is the deadline of Summer of Code 2008 which means pencils down after working on the code for about 3 months. In this last day as I promised after first beta, I'm releasing beta 2 which is more robust than the first one. A brief list of changes is as follows:

  • Language files are now ready
  • Database upgrade logic is added for easy upgrade to future releases
  • All known issues listed are fixed
  • Field types are modified in order to make install/uninstalling them possible in the next release

Future Development

You may ask if the development will finish with SoC today. But the answer is definitely no. This is only the first part and it'll be stable after some bug fix releases and development will still go on after that. In fact I could tag this release as RC as it was my original intention in my application. But I wanted to have some more beta time to make it more bug free. I'm hoping to open a site dedicated to this component for better support and communication after project completely finishes.

Download

Download Extend 1.0.0 Beta 2

 

Show other articles of this author

49 Votes

7 Comments

Feed
  1. Parse error: syntax error, unexpected T_STRING, expecting T_OLD_FUNCTION or T_FUNCTION or T_VAR or '}' in /hp/++/++/++/www/hp/+++/administrator/components/com_extend/controller.php on line 16
  2. Are you going to continue this work. It would be great if so, since this is a feature I'm missing from joomla that drupal provides.
  3. I guess this is dead in the water. It uses a separate set of articles total independent of Joomla's Article Manager. And it looks like Ercan is too busy to respond to the support questions. Any other alternatives any one?
  4. This is amazing. Few more field types are required. like

    Date, year, zipcode.....

    Why is this component pointing to a new set of articles and category. Why shouldn't it be extending the Joomla core articles?

    How to see the articles in the front end?

    One more suggestion, in the textarea type, you have given restriction for numbers[0-9], alphabets[a-z] and both. This might be a constraint if someone is building other language or unicode.

    These parameters must be part of the language .ini file. So if somebody is writing a language file, they might wish to choose the range of alphabets of their language. Mostly it would be in the unicode.
  5. Hi Ercan, I've installed your component and have it to the point where I've set everything up but I'm not having any luck getting the fields to show up on the front end. Thanks to your instructions, I've set up an article override in a new directory. That's all working fine and my changes reflect. But I think I'm not using the right syntax to pull the fields out of the fields array. Say I have a content type named "gallery", and a radio button field called "framed" (with yes/no). What would be the right code to echo the $this->fields object? Thanks I really glad for what both you and Jaap are doing. -Jason.
  6. Great Job! I would like to know what you think about a problem presented here and i pointed to your component as a potential solution: http://forum.joomla.org/viewtopic.php?f=470&t=318203

    Regards,
    Abdo
  7. Very interesting job... i have some questions:

    1) Is it possible for users to publish articles of a special type? How?

    2) Are fields searchable? For example, could I search for all articles in which the field "teacher" contains the value "prof. Smith"?

    3) Can I see a list of my fields? For example, a list called "teachers" which displays "prof. Smith", "prof. White", etc.; so that clicking on one item I can see all articles containing that value in the field?

Add Comment


    • >:o
    • :-[
    • :'(
    • :-(
    • :-D
    • :-*
    • :-)
    • :P
    • :\
    • 8-)
    • ;-)



    Click to get a new image.