FrontPage Server Extensions EOL June 30, 2006

Who still uses FrontPage? Luckily, none of our clients uses it.

Thanks for the information -- I'll be sure not to include it in our service offerings. Like you, we don't want to support anything that is at the EOL.
 
I dropped frontpage from all the servers I manage, no one has complained so I dont think anyone used them.

BTW does this mean that DA can stop putting ServerRoot /etc/httpd/ at the top of every virtualhost file, I moved my httpd into /usr/local so I now run a script which goes through every virtualhost file and changes /etc/httpd to /usr/local cause its not something which is templated, its actually in the directadmin binary (viewable with strings)
 
yay, finally that POS has died :P

It was a bugger trying to support people who had questions when i never took the time to learn how they worked :P
 
We intend to support FPX on already configured servers as long as DirectAdmin does. I don't know where JBMC gets the binaries. If they get them on demand from any public server, they won't be able to get them anymore, but if they have them, they can continue to use them as long as they'll work.

We're still installing FPX on new servers but will probably stop soon except on request.

Is there an easy way to disable FPX from the skins without writing custom skins?

Jeff
 
Hello,

I think it will likely stay as is for the time being.
We have our own copies of the frontpage binaries.
Should any security issue arise (or any good reason), I won't hesitate to remove them from the install. I may possibly just leave them as an option, just like zend.

As for the skins, they'd have to be edited to remove the links/files for frontpage. Frontpage doesn't currently have any options or on/off tokens to use in the DA skins.

John
 
DirectAdmin Support said:
Yes, that was added a few versions ago.
http://www.directadmin.com/features.php?id=754

Add:
Code: 
frontpage_on=0
to your directadmin.conf, restart DA, and frontpage is no longer in the skins.

John
Click to expand...

John.. Why don't you make this a browser based option instead of an SSH solution???...

I will bet that more than 50% of your customers have no idea that they will have to become profficient in the use of SSH before they purchase your software. :(

This response

DirectAdmin Support said:
Yes, that was added a few versions ago.
http://www.directadmin.com/features.php?id=754

Add:
Code: 
frontpage_on=0
to your directadmin.conf, restart DA, and frontpage is no longer in the skins.

John
Click to expand...

does absolutely NOTHING for the person that is not familar with all the files in your software nor does it help the person that is non proficient in the use of SSH..

Maybe you guy's should post a notice in bold on your website to the unwary ones.

If you don't want to incorporate a browser based solution as is being discussed over here http://www.directadmin.com/forum/showthread.php?t=19134, for those of us that are not experts in the use of SSH and or the files structure of your software, please post a step by step process one has to follow in order to turn off or remove frontpage :(
 
Last edited:
RadMan:
Code: 
[FONT=monospace]perl -pi -e 's/[/FONT]frontpage_on=1/frontpage_on=0/' /usr/local/directadmin/conf/directadmin.conf[FONT=monospace]
[/FONT]echo "action=directadmin&value=restart" >> /usr/local/directadmin/data/task.queue
/usr/local/directadmin/dataskq
 
smtalk said:
RadMan:
Code: 
[FONT=monospace]perl -pi -e 's/[/FONT]frontpage_on=1/frontpage_on=0/' /usr/local/directadmin/conf/directadmin.conf[FONT=monospace]
[/FONT]echo "action=directadmin&value=restart" >> /usr/local/directadmin/data/task.queue
/usr/local/directadmin/dataskq
Click to expand...

Hi Martynai... If that is code to kill Frontpage I already killed it awhile ago this way:

http://www.directadmin.com/forum/showthread.php?t=19134&page=2&highlight=frontpage+extensions

Only toook a few hours for this newbie to figure it out...

BTW... Thanks for your help there a few weeks ago but the access to old Betsy (the RAQ 550) finally got so bad, I had to shoot it and put it out of it's misery and mine.. :D

Cheers...
 
I will bet that more than 50% of your customers have no idea that they will have to become profficient in the use of SSH before they purchase your software.
Click to expand...

Server admins already know how to do thing via command line. DA is not supposed to be a replacement for a server admin.
 
If you want a product where you don't have to use the command line to do things then DA is not for you.

While DA does not state specifically that proficient use of ssh is required they do specifically state that ssh is required and that you must have root access to the server. Install Requirements. This implies that you need to know basic commands to manage your server. Proficiency is subjective. I don't even consider myself to be proficient because I learn something about certain commands almost every week. I don't think anyone here would say that proficiency in server commands is required to simply edit a file.

And as I have stated before I would rather the DA staff concentrate on satisfying my customers rather than trying to do what most server admins can already do. Adding the ability to hide the FP link is great but now lets move on to something our customers can truly use.
 
Last edited:
Another tip, if you want to be able to edit system files from DA you can do so from the DA File Editor at the Admin level. Login with SSH one time and add the edit_files.txt file to the edit_files.txt file and then from the browser you can add more files and be able to edit them from the File Editor. There is an increased security risk doing this since anyone who was able to break in to DA as admin would then be able to modify whatever file they wanted. But somebody who wants a browser based solution for everything is probably not concerned about the security of their server anyway. Use at your own risk.

The other thing you can do is add the files you want to be able to edit as you need them instead of adding the edit_files.txt to edit_files.txt.

Just remember that some of these files are meant to be edited through SSH instead of a browser for a reason, which is security.
 
On my opinion the problem is not really if I need to edit files using SSH or not. The main problem I see is the lack of documentation. There's no place to check all the avaliable options I can turn on/off unless I go thru all IDs on the features.php page and read them all. That sucks so badly. :(
 
This provides most documentation for the directadmin.conf file:
http://www.directadmin.com/search_versions.php?query=directadmin.conf

You could also open the directadmin.conf file. Most everything is self explanatory.

The documentation may not be to your liking, or even most people's liking or even my liking. But most all answers can be found. I have asked very few questions on this forum because most questions have already been answered numerous times or its in the Knowledgebase or in the version history section.

This question about FrontPage for instance could have been looked up here http://www.directadmin.com/versions.php

Finding information is an art and it can take a lot of time to learn. But its time well spent as you will be able to find the answer to anything not just about DirectAdmin.
 
freshmint said:
On my opinion the problem is not really if I need to edit files using SSH or not. The main problem I see is the lack of documentation. There's no place to check all the avaliable options I can turn on/off unless I go thru all IDs on the features.php page and read them all. That sucks so badly. :(
Click to expand...

You'll get no argument from me on that one even though there are people on this forum that have nothing better to do other than hunt for answers to solutions which could be simplifed by the authors of the software within minutes... :rolleyes:
 
Last edited:
which could be simplifed by the authors of the software within minutes
Click to expand...

Wow you really think that it would just take a few minutes to write all of that documentation. Excuse me I mean rewrite since it has already been written.

I have never spent more than a couple of minutes looking for any DA answer. I think the documentation already in place is quite easy to search.
 
floyd said:
Wow you really think that it would just take a few minutes to write all of that documentation. Excuse me I mean rewrite since it has already been written.

I have never spent more than a couple of minutes looking for any DA answer. I think the documentation already in place is quite easy to search.
Click to expand...

Yeah, it's ok, sure the information we need is here. But it surely could be way better. I don't need a GUI to configure stuff, but we could at least get a better documentation regarding the options we have. It's not like I'm asking HOW TO's. ;)

I'm sure John would also receive a lot less emails on support regarding these little configurations. Documentation is needed in everyway when you're developing software (and there's plenty examples over the web). It's just a matter of thinking in the long run.
 
You must log in or register to reply here.
Back
Top