Wednesday 14 February 2007 12:53:46 am

I will test that.

Thanks!

Wednesday 21 February 2007 12:55:52 am

Ho, i was just starting to code it cause i had many things to finish before (pagination, small modules etc )
So, i thank you VERY MUCH.

But... Never used workflow with ez publish, can you help me a little? (i'll go watch some tutorials but yours is working as standards?)

Wednesday 21 February 2007 1:21:04 am

You're great man!
I'll see what i can do alone with your workflow for now.

Wednesday 21 February 2007 3:30:11 am

I don't know how to thank you.. But... THANKS

Wednesday 21 February 2007 5:55:42 am

(Ok forget it, I just forgot to clear the cache, i'm so damn bad)

The only thing that bother me is that you can chose "membership approval", and i can't.

This workflow has a dependencie? (i just downloaded your other extension, just in case ^^)

Wednesday 21 February 2007 8:24:37 am

I installed it as you screened it but:
-I don't have the "Affected versions" field (choice)
-No mail is sent to the user when i configure user account settings

I must have done something wrong...

Thursday 22 February 2007 12:37:18 am

Yes, i have Ez 3.8.0.

Maybe i was not very clear, but what i want is that an email is sent to an user when his account is "enabled" by the admin (when he registers, his account is "disabled" and he must wait for the admin to enable it, but he never knows when the admin does it!).

The admin enables the account through "User account setting", in both front and back office (though it seems a little buggued in front).

Sorry for my poor english.

Thursday 22 February 2007 1:06:33 am

I overrided the file design/standard/templates/user/registrationinfo.tpl so that for 2 profiles the mail sent to the user doesn't include the link that validates the account.

Way used by default and for 8 profiles:
{'Your account information'|i18n('design/standard/user/register')}
{'Username'|i18n('design/standard/user/register')}: {$user.login}
{'Email'|i18n('design/standard/user/register')}: {$user.email}

{section show=$password}
{'Password'|i18n('design/standard/user/register')}: {$password}
{/section}

{section show=and( is_set( $hash ), $hash )}

{'Click the following URL to confirm your account'|i18n('design/standard/user/register')}
http://{$hostname}{concat("user/activate/",$hash)|ezurl(no)}

{/section}

What i did for my "special" profiles (maybe wrong way):
{'Thank you for registering at FRANCE-GAME.ORG, you will receive your registration email confirmation.'|i18n('design/standard/user/register')}

{'Email'|i18n('design/standard/user/register')}: {$user.email}

{'Your account information'|i18n('design/standard/user/register')}
{'Username'|i18n('design/standard/user/register')}: {$user.login}

{section show=$password}
{'Password'|i18n('design/standard/user/register')}: {$password}
{/section}
{user|attribute(show)}
{section show=and( is_set( $hash ), $hash )}

{'Click the following URL to confirm your account'|i18n('design/standard/user/register')}
http://{$hostname}{concat("user/activate/",$hash)|ezurl(no)}

{/section}

{'Link to user information'|i18n('design/standard/user/register')}:
http://{$hostname}{concat('content/view/full/',$object.main_node_id)|ezurl(no)}

(I know section is deprecated but the project was started by an other developper so i just did like him)

In fact, i just removed the link, so the user can't enable his account himself.

Tuesday 27 February 2007 1:03:09 am

Ok thanks!

By the way, i used your extension, it's very useful to handle new publications.

Thanks for everything.