General :
K-Meleon Web Browser Forum
I'm starting a new thread as response to this post:
http://kmeleonbrowser.org/forum/read.php?1,125632,156447#msg-156447
Differences between PortableApps.Com and regular structure:
You'll see certain folders or directories within K-Meleon mentioned frequently. In the PortableApps setup, the "K-Meleon" or root folder is located at:
The rest of the file structure is the same except the automatic updater will completely rewrite the some folders to ensure a clean update to the browser. So don't make modifications in the following folders or they will either break, revert, or corrupt after updates:
A note about KMEXT:
The K-Meleon Extension manager is not necessary to install K-Meleon extension packages (.7z). John mentions this in the thread linked above. You can find more information under Manual Installation in the documentation: http://kmeleonbrowser.org/wiki/Extensions#manual
I'm going to explicitly reccomend that you do it this way for PortableApps.com because of the way it handles updates. The auto-update will rewrite the "Browser" folder each time. So if an extension package contains any .xpi files in Browser/Extensions, copy those instead to your profile so that updates will not disable them. For example, in Rodocop's AdBlock Plus package there is one .xpi file for ABP so you would first move that to PortableApps/K-MeleonPortable/Data/profile/extensions and then you would copy the remaining files to PortableApps/K-MeleonPortable/App/K-Meleon/ and ABP would then continue to function correctly after updates. If you don't see a Browser/ folder in the package, you won't have to worry about that, and can install the package normally.
Also note that KMEXT is a great resource for older extensions but that it has not been updated since KM75 some years back. So the packages that say they're compatible with version 7x just mean up to 75, not up to the current version 76. There are also some extensions which rely on external services which may have changed since the last upload to the archive.
And finally about Firefox-style extensions and macros:
K-Meleon macro modules (.kmm) are single files that you can just drag and drop into your K-Meleon/macros folder or profile/macros/ folder. They will work the same.
The XUL-based extensions including legacy Firefox extensions, use a Mozilla extension manager that is built into the browser. You can manage them from the "about:addons" page. For example, if you check out Reality Ripple Software's About Add-ons (Legacy) you can just click the .xpi link or install it locally after downloading. K-Meleon will be default install XUL-based extensions to your profile and they will also work the same.
General discussion about K-Meleon
PortableApps.com (differences, extensions, etc.)
Posted by:
RJJIII
Date: August 23, 2022 01:24AM
I'm starting a new thread as response to this post:
http://kmeleonbrowser.org/forum/read.php?1,125632,156447#msg-156447
Differences between PortableApps.Com and regular structure:
You'll see certain folders or directories within K-Meleon mentioned frequently. In the PortableApps setup, the "K-Meleon" or root folder is located at:
PortableApps/K-MeleonPortable/App/K-Meleon/And the profile folder is located at:
PortableApps/K-MeleonPortable/Data/profile/
The rest of the file structure is the same except the automatic updater will completely rewrite the some folders to ensure a clean update to the browser. So don't make modifications in the following folders or they will either break, revert, or corrupt after updates:
- Browser/
- Browser/extensions
- Browser/defaults/settings
A note about KMEXT:
The K-Meleon Extension manager is not necessary to install K-Meleon extension packages (.7z). John mentions this in the thread linked above. You can find more information under Manual Installation in the documentation: http://kmeleonbrowser.org/wiki/Extensions#manual
I'm going to explicitly reccomend that you do it this way for PortableApps.com because of the way it handles updates. The auto-update will rewrite the "Browser" folder each time. So if an extension package contains any .xpi files in Browser/Extensions, copy those instead to your profile so that updates will not disable them. For example, in Rodocop's AdBlock Plus package there is one .xpi file for ABP so you would first move that to PortableApps/K-MeleonPortable/Data/profile/extensions and then you would copy the remaining files to PortableApps/K-MeleonPortable/App/K-Meleon/ and ABP would then continue to function correctly after updates. If you don't see a Browser/ folder in the package, you won't have to worry about that, and can install the package normally.
Also note that KMEXT is a great resource for older extensions but that it has not been updated since KM75 some years back. So the packages that say they're compatible with version 7x just mean up to 75, not up to the current version 76. There are also some extensions which rely on external services which may have changed since the last upload to the archive.
And finally about Firefox-style extensions and macros:
K-Meleon macro modules (.kmm) are single files that you can just drag and drop into your K-Meleon/macros folder or profile/macros/ folder. They will work the same.
The XUL-based extensions including legacy Firefox extensions, use a Mozilla extension manager that is built into the browser. You can manage them from the "about:addons" page. For example, if you check out Reality Ripple Software's About Add-ons (Legacy) you can just click the .xpi link or install it locally after downloading. K-Meleon will be default install XUL-based extensions to your profile and they will also work the same.
English