[idea] Landing Page Presets

[WatskeBart]

I would like to suggest a preset option for the landing page configuration.

With all the different landing pages out there, it would be nice to save a current landing page to a preset, so you can recall it later and switch quickly between them.

Unfortunately i don't have the PHP coding skills to do so :P but it never hurts to suggest :)

[PineDominator]

I would like to suggest a preset option for the landing page configuration.

With all the different landing pages out there, it would be nice to save a current landing page to a preset, so you can recall it later and switch quickly between them.

Unfortunately i don't have the PHP coding skills to do so :P but it never hurts to suggest :)

def needed, I noticed a couple modules that need access to it as well potential for problems? one fighting with the other

[PineDominator]

basically we need something like cron tabs but with only one module/script allowed at one time. a system to let others IE modules/scripts know one is selected already, so you have to disable that one or click allow change in a pop up and potentially let that module know as well in case it needs to shut itself off.

something like this in place for any features that could use it, sometimes you need dnsspoof but maybe a module can't function with it enabled

have a definition system where a module can define it's needs and when you try to turn one on and it's checked to see if any other module is using those resources to warn the user.

Edited April 24, 2012 by petertfm

[WatskeBart]

I think i don't fully understand what you try to explain. (because the lack of my english that is)

I already noticed for example that the module keylogger backs up the current landing page before it substitutes his own. (hence the keylogger install/uninstall function).

I thought it would be as simple as putting a input bar with a save button, so you can name your preset and it will save the preset to eg. /www/pineapple/lpage/nameofpreset.php and add it to a dropdown menu next to the landing page configuration area.

When you select a preset from the dropdown menu and click a activate button, the nameofpreset.php will be moved and renamed to /www/pineapple/index.php

I don't understand how that should interfere with a module, as the pineapple user is responsible for backing up his landing pages.

Just spit balling here B)

[PineDominator]

I think i don't fully understand what you try to explain. (because the lack of my english that is)

I already noticed for example that the module keylogger backs up the current landing page before it substitutes his own. (hence the keylogger install/uninstall function).

I thought it would be as simple as putting a input bar with a save button, so you can name your preset and it will save the preset to eg. /www/pineapple/lpage/nameofpreset.php and add it to a dropdown menu next to the landing page configuration area.

When you select a preset from the dropdown menu and click a activate button, the nameofpreset.php will be moved and renamed to /www/pineapple/index.php

I don't understand how that should interfere with a module, as the pineapple user is responsible for backing up his landing pages.

Just spit balling here B)

It's more about if you install multiple modules that use the same resources they will fight with each-other.

[WatskeBart]

Understood but there is only one /www/index.php so first come first serve i guess.