Somehow adjustments I am doing to the CSS files of the theme aren't visible on the site. And it's a bit complicated to check which files are used (e.G. which use agent has been identified), since the CSS used is some file in /files/css and not the actual CSS files from the mobile theme folder.

I'm using Drupal Version 5.10 with Mobile tools installed.

Can someone tell me why my changes aren't visible?

Comments

znero’s picture

I jus tried, it doesnt even matter when i remove the css folder completely. It doesn't seem to be used at all.

scottsawyer’s picture

I have been working with Nokia Theme for a couple of days, trying to get a handle on the CSS, and have had some struggles figuring it out.
I could be totally wrong, but here goes:
I think the CSS in the files/css folder are cached versions the theme complies, not ones you can actually edit (if you go to files/css, nothing there)
a lot of the styling is performed in the baseStyles.css (css/ (low || mid || high) , and they seem to over-ride the style.css in the theme root
make sure you clear the cache (Admin-Settings-Performance ** edit - forgot that Mobile Plugin has it's own cache flush utility, so try that one **, and on your browser) after changes, before you reload your page

Another struggle for me is testing each of the settings, using Mobile Plugin. I choose to test the High with Touch mode, but it will only show me Low.

Slightly off topic, I would really like to show different content to mobile users, but doesn't seem too feasible with out a ton of work. I am using a lot of panels with views. Maybe there is a mobile context that can be used?

Hope this helps. I will be back often while I build out my mobile site.

znero’s picture

Yes, the stuff in files/css seems to be compiled and I delete all content of that folder every time I make a change.

Changing style.css in the theme folder works, as soon as I delete those files and new ones are created. Changes to baseStyle.css in any of the low/mid/high folders, however, won't work.

Where did you find the cache flush utility of the mobile tools? Maybe it's not in my old version.

I just found out that I can deactivate "Aggregate and compress CSS files" in the performance menu, this seems to build those files in files/css. Let's see if it helps.
Edit: Now that I can actually see the CSS files being used (in Firebug) I see that only style.css is used without any of the other files.

Which mode of device detection are you using?

scottsawyer’s picture

I am using Mobile Plugin, not Mobile Tools, but in the Mobile Plugin, it is on the Settings tab.

For device detection rules, here is my setup:
* Edit rule: USERAGENT =~ Windows NT PPC Mac OS X Intel Mac OS X ? group=no (weight=1)
* Edit rule: USERAGENT =~ Series60/5.0 Maemo iPhone iPod webOS ? group=nokia high-end with touch,1 (weight=2)
* Edit rule: USERAGENT =~ Series60 webKit Android ? group=nokia high-end with touch,1 (weight=3)
* Edit rule: is_wireless_device == true ? group=nokia low-end (weight=10)

I did turn off "Optimize CSS", which helps, probably should turn on after design work it finished.

Are you having more luck?

atrasatti’s picture

Assigned: Unassigned » atrasatti
Status: Active » Closed (won't fix)

Guys,
there are 2 possible scenarios:

  • Using a plugin that automatically selects the right theme
  • Using only one theme and selecting it from the admin panel

The second case is the easiest and the admin has full control.
The first case, which applies to both of you, is more powerful, but also more complicated and it will often ben hard to understand exactly what part of the code is doing what (the plugin or the theme). In a way, the Nokia mobile theme is a bit too smart than it should be.

Either way there are two parts of template.php that you should be looking at, phptemplate_preprocess_page() and _nokia_mobile_device_detection(). In phptemplate_preprocess_page the theme checks if you are using the Mobile Plugin, if so, it uses the detection provided by that, otherwise uses the internal detection as defined in _nokia_mobile_device_detection. The combination of these two functions determines which CSS and JS files will be provided.

You probably want to add some debug code there to see what really happens and then make sure the plugins you are using are configured to work at best with your current setup.