supportpal / supportpal-resources Goto Github PK

Directory

https://github.com/supportpal/supportpal-resources/tree/languages/lang/es

Updated up to version

2.1.0

Known Issues

• Needs updating to latest release

Directory

https://github.com/supportpal/supportpal-resources/tree/languages/lang/sv

Updated up to version

2.3.0

Known Issues:

• installer.php needs translating

Please update this repository to the latest version

Directory

https://github.com/supportpal/supportpal-resources/tree/languages/lang/fa

Updated up to version

2.0.0*
* barely translated - lots of missing translations

Known Issues

• All files need translating

Directory

https://github.com/supportpal/supportpal-resources/tree/languages/lang/de

Updated up to version

2.0.3

Known Issues

• Needs updating to latest release

Directory

https://github.com/supportpal/supportpal-resources/tree/languages/lang/fr

Updated up to version

2.1.1

Known issues

• Several missing translations throughout most files
• Needs updating to latest release

Let's say you want to start a new theme. You would have to:

• Copy templates/frontend/default into templates/frontend/your-theme
• Select the theme in SupportPal

Although this works there is a critical flaw. You can't keep track of changes in new releases with the help of git. You would have to go over the Supportpal commits, check what changed and copy it manually into your own theme. You're not taking full advantage of what git has to offer.

The only way to get git to do its magic today is to:

• Clone this repository
• Create a new branch
• Make your changes in the default theme
• Merge the changes from Supportpal back in when there's a new release

The reason for this is because the assets folder includes static files for the frontend and backend. I don't understand why yet but it makes sense to include them in the actual template.

I would propose to change it to something like this:

|-- assets
|   |-- general
|   `-- installer
|-- lang (own repo)
|   `-- en
`-- templates
    |-- errors
    |-- frontend (own repo)
    |   `-- theme
    |       `-- assets
    `-- operator (own repo)
        `-- theme
            `-- assets

That way you can work on your theme in a similar way as this:
https://github.com/WHMCS/templates-six/#command-line-usage

Which makes Supportpal upgrade friendly.

Directory
https://github.com/supportpal/supportpal-resources/tree/languages/lang/nl

Updated up to version
2.2.0

Known Issues:

• installer.php needs translating
• update to latest release