[SOLVED] Custom WAPT and selfservice package

[Mickael]

Hello,

our association's logo was recently changed.
We imported the custom-waptexit-and-selfservice package from the store, edited it, and added the new .png and .ico files.
We tested the package locally, and it works.
We then deployed the package across the entire network, but here's the problem:
it seems that the old logo, which exists somewhere on the server, is overwriting the new one, and we don't know where this old logo might be located.
We weren't involved in the original WAPT server installation; I don't know what was done at the time.

On the server, in opt/wapt/templates, the correct logos are indeed present.
On the machine, in C:\Program Files (x86)\wapt\templates, the correct logos were replaced with the old ones without request.

WAPT Version: 2.6.1.17472
Server OS: Debian Bookworm
Machine OS: Windows 10/11

Thank you

[htouvet]

Hello Mickael,

Since version 2.6.0.17279, custom logos and templates must be placed in

Code: Select all

C:\Program Files (x86)\wapt\custom_templates

This ensures that they are not overwritten during a Wapt upgrade.

The package template that is on our repository for customizing logos is not up to date.

The code needs to be modified as follows (replace templates with custom_templates):

Code: Select all

# -*- coding: utf-8 -*-
from setuphelpers import *

def install():
    # print("N oubliez pas d utiliser la fonction d update package pour stocker les images en amont")
    # print("Make sure to use update_package function before installing the pkg")
    # print("La taille recommandée du logo est de 200X55px et le format .png")
    # print("Recommanded size is  200X55px and .png format")

    wapt_template_path = makepath(WAPT.wapt_base_dir, "custom_templates")

    for png in glob.glob("*.png"):
        print("Copying: %s" % makepath(wapt_template_path, png))
        filecopyto(png, wapt_template_path)

Sincerely,

Hubert

[dcardon]

Hi again Mickaël,

sorry about the outdated documentation and package. I've escalated the issue internally to correct the documentation and package. I'm marking the topic as resolved.

Regards,

Denis