HTML Logo by World Wide Web Consortium (www.w3.org). Click to learn more about our commitment to accessibility and standards.

Moving forward with Composr

ocPortal has been relaunched as Composr CMS, which is now in beta. ocPortal 9 will be superseded by Composr 10.

Head over to compo.sr for our new site, and to our migration roadmap. Existing ocPortal member accounts have been mirrored.


You may get PHP errors about a theme.ini file not being able to be parsed - Comments

Login / Search

 [ Join | More ]
 
Title You may get PHP errors about a theme.ini file not being able to be parsed
Description This seems to affect a minority of users with custom themes.
Affects Unknown
Fix sources/support.php attached
Fix files support.php

Back to the top

Comments / View



Avatar
I've noticed that although my exported tar file contains my edited 'theme.ini' mod, after the addon import was deployed the last parameter 'supports_wide=0' has been removed and must be edited-in again. There is no error message involved.

I'm wondering if this is because the basic theme was previously not set to 'Fixed-width' and the system will apply this adjustment to the new theme.ini.

Avatar
Hi,

I tested this and I did find a bug when you edit a theme where it wipes out all the settings that aren't in the user interface. I'm fixing that and I think really everything should be in the interface, so I'll add it all.

There was no bug when importing/exporting addons, although when you export an addon then go to addon management, if you see the addon in the list it is a version you have previously imported (i.e. old version), not just what you exported. This is because exported and imported addons are stored separately.

Avatar

Chris Graham said

There was no bug when importing/exporting addons, although when you export an addon then go to addon management, if you see the addon in the list it is a version you have previously imported (i.e. old version), not just what you exported. This is because exported and imported addons are stored separately.
Chris, I’m not sure I understand this part!

Here’s how I create my themes:
1-Establish a brand new development platform (clean install of latest version)
2-Export developped theme
3-Create a final test platform (clean install of latest version) and import theme new theme
4-Test imported theme, apply corrections if any
5-Export Final Version

What I understand from your statement:
  • In my case, I should always find a previous (old) theme on the “Export Theme List”
Is this under “/imports/mods/”?
  • Never checked that before as I was using the Export from Theme manager
The list also contains:

  • /pages/comcode_custom/EN/
  • /themes/
In my case, in view of my ‘development process’, am I to understand that it is better to checkmark the files I want to export from that list?

Avatar
No, I just meant there may be some confusion going on. Reading that, I don't think there is. So to save confusion I think it's best to leave it there.

I think probably at some point you just went through the "Edit theme" screen (where you change the theme description, permissions, etc) and it wiped your customisations. This is the bug I mentioned is now fixed :).

Avatar
OK, Thanks!:)

There are too many online users to list.
Control functions:

Quick reply   Contract

Your name:
Your message: