No sorry, forget what what I said about radio options.

Im trying to use the related article field - but get it to show the article title instead of the article ID

himgoku wrote:


Hi @himgoku,

nothing with "ns"...

Any other ideas?

@adonay

Doesn't work for me. What does work is saving the field storage as:
Standard | Article| field_name | Alter | Text


I really thought it was "ns"
Ok this works, but you have to change line 114 of sd_field_concat.php:

into this (delete the space between ' '):

This results in a no space as default separator. If you change your mind afterwards, you can always add a space in the front end Value Separator field....

@simon


I understand and I can live with your alternative for the time being... I guess I just have to wait until someone creates a global search field. Keep up the good work, Simon!

regards,
Himgoku

@all,

I have updated to version 2.0.7 which does no implement the 'ns' separator value when no separator is needed, so no need to hack the core. Apologies for this! Length of the field list also changed to 1000 characters now.

@himgoku wrote:


The SD Concat Field is like any other field, it can be stored anywhere. As far as changing the length of the actual SD Concat's "field list" input goes, I have changed this length to 1000 characters in the core now.

Kind regards,
Simon

@all,

Just updated SD Field Concat plugin again, this time to version 2.1.0 and it brings with a feature I know all of you have been wanting:

The ability to get the next auto increment value of any table in your database. This means no more headaches when it comes to getting unique titles and alases as you can rely on the next auto increment value to be accurate.

For those worrying about UPDATING an article, stress not. If an article is NEW, the next auto increment value is added to an INI file as a key => value pair where key is the ID of the article you're working in and value is the auto_increment of the table of your choice. Once it's been added to the INI file, it will be read from there in the future.

So an INI entry of 21=45 will mean that article with ID 21 had an auto increment value of 45 for whatever table you chose. This could have been the users table, content table, ANYTHING. The reason I did this was because obviously when you are updating an article, you do not want that value to change.

I hope this makes sense and I hope this is of huge use to you!

SEE THE FIRST POST OF THIS THREAD ON PAGE 1 TO GET THE LATEST VERSION 2.1.0

Kind regards,
Simon

Greetings,
Excellent work Simon! You are terrific.

What other gems are you working on?

Thanks for all your efforts,
Matthew

@Matthew - Thank you!

Not much at the moment to be honest. I needed to expand this plugin for my own needs, so thought I'd benefit the community at the same time.

Kind regards,
Simon

@all,

I have updated to version 2.1.1 as there were issues with the way the INI file was handling both new and updated articles.

Currently the storage procedure for incremented records is as follows:

Add a new article:
art_id=increment_id where where 'art_id' is the ID to be of the current article and 'increment_id' is the next auto ID of the table you specified in <table>.
The art_id=increment_id key value is stored in an INI file.

Updating an article:
INI file is parsed and checked to see if key 'article_id' exists where article_d is the article you are updating. If it DOES exist and it has a value, that value is used. If it DOES exist but DOES NOT have a value, the auto increment of <table> is retrieved and assigned to the key 'article_id'. If the key does not exist (ie the article ID is not in the INI file) a new key value pair is made in the same manner as when making a new article, and reference using the current articles ID.

IMPORTANT:
Manually deleting the value of a given key in the increments.ini file (stored in plugins/cck_field/sd_field_concat/) will result in that value being newly generated the next time you update that article.

A simple scenario:

- You add a new article that use the next ID of table 'users'
- A next ID of '45' is retrieved and reference to article '6'
- The INI entry looks like this: 6=45
- 6 new users are added, making the next auto ID 51 now
- You manually remove the value for key (article) 6 in the INI file
- The INI file now looks like this: 6=
- You update article with id (key) 6
- The new auto ID for table <users> is fetched
- The INI file is updated
- The INI file now looks like this: 6=51

I hope you get the drift.

You can download version 2.1.1 on post #1 of this thread! ENJOY!

Regards,
Simon

it does not work for me








Patrick

erase the first | use only $date||$time

it makes no difference

Hi and thank you for a great plugin.

The problem is i just can't get it to work. Don't know what dumb mistake I'm making. Read all forum posts and tried everything.

I want when the user registers, his/her profile article must bear their name, from the name field, as the article title. Try as I may, I fail all the time. When I insert [Profile of]||$name||$date then I get Profile of $name $date. When I input [Profile of]||#name#,#date# I get Profile of (empty).

I'm sure the solution is so obvious, I'll be left red-faced.

Thanx in advance

Hi Sidekick,

unless mistaken, try: [Profile of]||#name#||$date

Obviously the field must be present in form as well as in content.
You will have to re-open the item in form view (try backend first) and save it .. so that it can be rendered in content(webview) once you'll refresh the page.

Good luck!

Hi pretobrazza

Thanx for your quick response. I tried your suggestion but it changes back to "Joomla user-##"

Thanx anyway

Hi sidekick,

Obviously #name# refers to some_field called 'name' in the same form as where you have the concat field. You do have such a field, not so?