Package bug?

[Desdinova]

I don't know if this is the right forum for this topic, but anyhow.

When editting a package and changing the name it creates a new package instead of renaming the older. which means I have to manually edit every user who's using the older package to start using the newer package.

 

[nobaloney]

Yes, saving under a name writes the page contents under that name. You may be able to rename manuallly; not sure, as I've never tried it.

Jeff

 

[Desdinova]

I see. Well my server isn't really near so I can't access the shell, which means I think it's a bug, not a feature

Imagine a big server (Direct Admin) cleanup session where you'll manually have to go to each customer to adjust his package. This would be much more of a problem than to create a simple manual copy of a package.

 

[nobaloney]

Perhaps DA staff will look and respond... but what has distance got to do with using ssh to shell into your server?

Jeff

 

[DirectAdmin Support]

Hello,

There is no "package rename" tool. The name entry when saving the package is just like the "File -> Save As" dropdown in windows. If it's the same name, it will overwrite the old one, a different name will create a new one.

To change all Users to a different package you have to change all users to a different package one by one (if you only have DA access).

If the settings also need to change (eg: bandwidth, quota limits, etc), I'd recommend that you first make the setting changes with the same name so that all users with the current package get that change. This has it's benefits because then you can manually go into ssh and type

cd /usr/local/directadmin/data/users
perl -pi -e 's/package=[b]oldpackage[/b]/package=[b]newpackage[/b]/' */user.conf

And the settings will already be what you want.

But there is no package renaming tool in DA.

John

 

[Desdinova]

ok thanks.
Why not if I may ask? It doesn't sound like a big something to really make it an edit tool instead of a save as tool.

@jlasman
I don't know how to get into my server's shell from here. Is that a DA feature or would I have to look somewhere else?

 

[nobaloney]

I'vew brought the thread to DA staff attention and they'll have to make a decision based on availability of programming resources.

Shell access to your system is dependent on your OS, and not on DirectAdmin. If you own your own system, your OS install should have set it up. If you don't own your own system, then your hosting company has to set it up for you, which they may or may not do, according to their policy.

Jeff

 

[Desdinova]

Ok thanks

I own the server, it's running on FreeBSD. Unfortunately I was incapable of setting the OS up, so that has been done by the provider. I don't know if they've set up the shell access. I'll send them a mail about this.

 

[mrjcleaver]

I need to rename a package!

So I see these messages from 3 years ago... is it still not possible to rename a package through the admin interface?

If not, is there a script to do it from the command line?

The interface made me think that if I changed the name at the bottom of the package page and hit save then it would rename the package. It doesn't: it CLONES the package.

Thanks for your help, M.