*edit to clarify path names
Using 6.12...
I started my development on a test server that I have here with a static IP pointed at it. Apache uses /var/www/ as the root, but when I started, I loaded everything into /var/www/drupal-6.12/
I did much of my development, and decided that I want to move the sites base address to the root of the server, ie: just the ip address.
So I did this: /var/www/ mv drupal-6.12/* .
which moved everything over to the root, as I had hoped.
My problem: I had installed the mobile module and theme so that mobile phones can access the site as well as normal browsers. After the move, the mobile them has been set to the default. I can go into my user account settings and select the proper theme (addari) but when I go to Adminiser>>site building>>themes to try to change the default theme, it doesn't change. I select the radio button, and press Save Configuration, but when the page reloads it says "The configuration options have been saved." but the radio button is back on Mobile, and that is still the default theme. I tried to disable that theme, and got the same results: It says that it changed, but nothing is changed.
I went back and moved .htaccess to the new location, but have not edited anything in there, just in case.
settings.php has write permissions, I tried clearing the cache, I looked in settings.php and $base_url was commented out. I uncommented it and set it to http://12.34.56.78 (Not the actual IP address...) but it made no difference.
I think I have tried everything that I can think of. Can anyone suggest somewhere else to look?
Thanks!
Comments
Can't change global theme setting after site move
Update: In order to make the site usable again, I moved everything back to the drupal-6.12 directory. I did nothing other than a mv command to do it. By pointing back to the folder in my browser, everything works normally.
It seems that there is a config file somewhere that the theme selection uses that must be using a hardcoded path rather than a relative bath from $base_url Anyone have any suggestions? I would hate to not be able to move the site to a live server when I am done...
_
So...... is this just an expected behavior? I have been searching the forums and have not found anything that helps my problem. From what I have read, moving the site should be a simple matter of moving the files, but it is not working in my case.
If Drupal is not going to be able to be moved, I guess I need to know that sooner rather than later. It will be a mess explaining to my boss why I have to start over, but better now than after I have finished building everything and it is trapped on a development box.
Thanks for all the feedback
More info
If I change 000-default in the sites-enabled directory to point to /var/www/drupal-6.12/ instead of just /var/www/ it does the same thing. I cannot make any changes at admin/build/themes
I change the check box or radio button, and press save configuration. Drupal tells me that the configuration options have been saved. I look, and nothing has been changed.
_
bump
Have you tried disabling the
Have you tried disabling the mobile theme and module in the database? Using phpMyAdmin, or your preferred tool, go into the system table and set the mobile theme status to 0 and your preferred theme status to 1. That should at least allow you to view your site as you intend while you try to figure out the issue.
_
I can try that, although in my original post I stated that for my logged in user account, I can set my preferred theme to the correct setting and it works for me. I can see the site as I want it while I work in it. The problem is that a non-logged in user only gets the mobile theme. I don't want to disable the mobile theme, as that is on the "must have" list for the site. I want the theme manager to work properly, which seems to not be the case.
Thanks for the suggestion. It's nice to see someone respond. A disturbing trend I have found while searching for the solution in this forum is that a lot of posts are ignored. I think in general it is a reflection of the product in how willing the developers are to support it. Sadly, many threads are 3 or 4 posts by the same person that eventually just gives up.
...
With all due respect mate, did you try to above suggestion? To bad if you have to temporarily disable the mobile theme, tough, if that fixes the issue then take the site offline and disable it for 5 seconds or whatever.
Have you checked the settings in the database - if so, why havent you reported them here?
Have you cleared the cache?
Do you have aggressive caching enabled?
In short, what have YOU done to fix the issue - we can't be expected to guess our way through what you have done already. If you have done nothing then why should we help you at all, you're not even exhausting existing suggestions.
6 bumps in 2 days does not endear yourself to the regular help, and I don't exactly see you answering other newbies questions either, yet you think we should help you when-ever it pleases you? Eat your own dogfood and stop the bitching.
Pimp your Drupal 8 Toolbar - make it badass.
Adaptivetheme - theming system for people who don't code.
_
Fair enough: The suggestion above was in the context of making the site viewable while I worked on it. Nonetheless, I looked in the system table. Addari status is already set to 1. Mobile status is already set to 0. It still only shows mobile when I go to the site without being logged in.
What settings should I check? Nobody has pointed me in any sort of direction. While searching the forums, all I find are other threads that are either not related, or where others have the same problem, get ignored, and give up.
I did clear the cache, as I stated in the original post.
Aggressive caching: No. Caching is disabled.
I Thought that I had listed several areas that I had checked in the top post. Most of what I listed as having done was suggestions and troubleshooting that I did based on other forum posts and directions for moving sites.
I am certainly not asking anyone to "guess (y)our way through". I listed what I did, and asked for help pointing me in the next direction.
As for endearing myself: What would you suggest? My first post was a detailed explanation of what I was trying to accomplish, what I did to get it done, what did not work, and a request for a simple nudge for where to look to move forward. I would have been happy with a link to an instruction page.
Instead, after a couple of "more info" posts, it gets frustrating not getting any assistance at all.
SInce I have been using Drupal for all of about 2 weeks, I am afraid that I don't have a large repertoire of expertise to offer assistance with. In other forums, I prefer to know what I am talking about before jumping in on other threads and making a fool of myself. Rest assured that were I able to offer help, I would.
Heres what I would do: 1.
Heres what I would do:
1. take the site offline
2. disable then delete both problem themes, or all contrib themes (leave garland enabled)
3. clear cache data
4. upload the themes again, configure as you want
Yeah, you have knowledge to share, even after two weeks, you've done some things and that's more than some others:)
Pimp your Drupal 8 Toolbar - make it badass.
Adaptivetheme - theming system for people who don't code.
since my first suggestion didn't work
I'll second this approach. It's no fun, but sometimes to identify the problem, you have to revert to Drupal core. Disable all addon modules and themes (via the database if you have to) and re-enable them one at a time, most important first. Sometimes just doing this resolves the issue, but at the least you should be able to see which module or theme is causing your problem.
Ok, here are the
Ok, here are the results:
With the site in it's functioning directory location, I took the site offline. I disabled all but garland. I then went into /sites/all/themes and deleted all of the add on themes. and cleared the cache.
Then, I moved the site to the web root as described in my first post.
Loading up my site, I get an all white page with my front page story on it. My primary key menu is across the top. I have no other menu, including the ability to do administration. I also have 3 error messages:
* warning: array_map() [function.array-map]: Argument #2 should be an array in /var/www/modules/system/system.module on line 966.
* warning: array_keys() [function.array-keys]: The first argument should be an array in /var/www/includes/theme.inc on line 1771.
* warning: Invalid argument supplied for foreach() in /var/www/includes/theme.inc on line 1771.
Digging up my weak php skillz, i dug into system.module and started back tracing function calls using grep. There is a db query in 965 that looks up the themes in the system table. The only one that is in the system table is minelli. There is a variable, $themes, that I believe is at the heart of the problem, but I cannot trace that back to where it is being set yet. It appears that the system is looking for a theme name that no longer exists.
Is there somewhere that I can make it rebuild the tables in the db after I have removed the questionable themes?
I will take the next steps of moving the site back to the old directory, which I suspect will make it administrate-able again. I will then remove all modules as well.
If that doesn't work, can someone verify for me that if I just delete my drupal-6.12 directory and do a clean install in the web root and point it at the existing tables, that my content (mostly pages and menus) will still exist? If so, I think that will be the least painful solution, as I don't have a lot of addon modules and themes, and it loks like I am deleting them all anyway.
Thanks!
2 quick questions: 1) is this
2 quick questions:
1) is this an artiseer theme you were using?
2) by any chance did you upload and forget about the same themes in the /themes directory (as opposed to sites/all/themes)?
try loading up /admin/build/modules
that will clear the theme registry.
From a google search I can see this is a common error, but I have never encountered it before.
Pimp your Drupal 8 Toolbar - make it badass.
Adaptivetheme - theming system for people who don't code.
Progress!
It is the mobile tools module. (not the theme)
I moved it back to the functioning directory. Took it offline, disabled all modules, cleared the cache, and deleted the directories for those modules.
Then I moved the site back to the webroot.
Everything looked good in garland, so I reinstalled the addari theme. Interestingly, it remembered all the settings for it, and it came up beautifully.
Next, I reinstalled FCKEditor, and enabled it. Still looking good logged in and out.
Installed mobile tools Module (not the theme) and as soon as I checked enable and saved configuration, the whole thing fell apart. Uncheck it, and it all came back.
Does the module save any configuration info in the DB? If so, I will go clear it out. If not, then I think I need to move on to a thread regarding the mobile tools module. Either way, I now know what the source of my trouble is.
jmburnz and rjoy, thank you, sincerely, for the help. I would have given up without the suggestions you gave. Sometimes a push in the proper direction is what is needed.
I will try to offer assistance in any thread that I feel qualified in the future. I just don't want to offer someone the wrong advice.
Thanks again! If you know about the module storing permanent data, let me know. Otherwise, I am off to dig through the DB.
probably...
I'm not familiar with the module in question, but most modules do create tables and save configuration settings in the database (which is why your configuration options were still associated with your theme). Look for tables in the database with 'mobile' in the table name. If there are none, you probably only need to look at the system table.
If you look at the module's
If you look at the module's code, it's usually pretty clear which tables it's writing to. Check the dot install file first, then check the code for SQL.
Not a perfect solution, but one that might send you in the right direction.
And if you've found the solution, please post it, or a link to it if you took it to the Mobile Tools page.
_
bump
_
Bump
I had this issue. I fixed it
I had this issue. I fixed it by removing the config file (settings.php) definition of the default theme:
This one!
I had a late night debugging session moving between servers and set this variable, then forgot I had done it! Read this then facepalm. Thanks for reminding me!