Update process installing adaptivetheme 3.2 as a subfolder of adaptivetheme 3.1

Not sure I follow the issue you're pointing out. Can you explain a little more? There should have been updates in AT Core, probably close to 21 files changed in the last day or so, changed to perhaps 245 lines.

Thanks for the positive feedback on the new branding/logo, I spent a lot of time on this with a designer and I'm really happy with it.

I have updated this twice, yet my system is still showing that the module needs to be updated.

mermentau - just delete at_core theme entirely and replace it and clear cache, something is probably wonky when over-writing the files etc.

groston - don't know, I have had some instability with the update status system the past few days, could be related, if you're running 3.2 that should not be happening, but if you're on DEV then it can happen every time I push new code to the branch.

I'll go and download the actual package from the project page and check it also.

#3 mermentau - are you talking about logos or the screenshots in the admin, because, believe it or not, I forgot to replace the actual logos in each theme with the new one... so only the screenshots in the Appearance settings have the new branding.

I have to cut a new release since I left some debug code in also (its safe to run, but needs to be removed, its not doing anything just sitting), that will happen tomorrow so I update the actual logos then also.

The problem is in the file adaptivetheme.info line 345:

; Information added by drupal.org packaging script on 2012-08-29
version = "7.x-3.1"
core = "7.x"
project = "adaptivetheme"
datestamp = "1346238662"

Should be:

; Information added by drupal.org packaging script on 2012-08-29
version = "7.x-3.2"
core = "7.x"
project = "adaptivetheme"
datestamp = "1346238662"

adaptivetheme.info of AdaptiveTheme 7.x-3.2 is fine. It contains

; Information added by Drupal.org packaging script on 2014-03-23
version = "7.x-3.2"
core = "7.x"
project = "adaptivetheme"
datestamp = "1395575059"

#6 - that's an old file, see it was packaged on 2012-08-29, so something is going wrong when your site/theme is being updated.

Drupal.org adds this stuff to the info file, no us project owners, it's entirely automated by the d.o packaging script.

So what could be the problem then? I have updated several times on several sites using this theme. I have tried auto and manual updating and have encountered the same problem all sites, all ways. I don't have the problem with other module updates. Hmmm.

I'm not sure, I downloaded the archive from the project page and I get the updated info file with new release/package date. That stuff is not in our usual git repo, it's only added at the point the archive packaging script runs, about 5 minutes after we create a new release node.

So yeah, I don't really know.

#2 The same here

This is not a bug in the theme so I am changing this to a support request.

I have answered this best I can, the version string in the download is correct, so why this is not working for you cannot be known to me, not without debugging your actual installation or Drupal core (right now I can't actually replicate the issue).

As I suggested do a manual update - that way you 100% know the correct files are on the server.

If you are still having problems I suggest you look at two possibilities:

1) Human, or a file transfer error (it's possible, check all details, some FTP programs tell you they sent/put a file, but did not).

2) The update system in Drupal core is broken (possibly for themes only).

In my case the problem was caused by the update process installing adaptivetheme 3.2 as a subfolder of adaptivetheme 3.1. I manually reinstalled it directly and Drupal now reports it being up-to-date. This happened on all Drupal 7 sites where I am using this theme. It did not happen with Pixture Reloaded.

I also ran into some weirdness updating Adaptive Theme, Sky, Corolla and AT Commerce on a multisite install. Worked fine on my local machine (Mac).
The main issue I found on a VPS host was that the new adaptivetheme directory was in the old adaptivetheme directory ie. sites/all/themes/adaptivetheme (3.1)/adaptivetheme (3.2)

The available updates also stubbornly refused to recognize the new versions even when the listing in /admin/appearance showed the new version numbers. Clearing caches a few times finally fixed it and reloading the appearance page in the browser loaded the new screenshot.png

Changing title, this might make it easier for others to recognise the issue, I'm going to open an issue in the drupal issue queue to ask why this might be happening.

A quick "me too": I have three wholly separate sites, on separate servers, running Adaptivetheme. All three exhibit this behavior: notification that an update is needed, perform the update, and get the same notification the next day. No apparent issue with file/directory permissions.

cd sites/all/themes/adaptivetheme/adaptivetheme
cp -a ./* ../
cd ..
rm -R adaptivetheme
(chown if needed)

Configuration / Performance / Clear all caches

may not fix the problem with update being installed into the subdir but it's no longer nagging about needing to update every day

The subject line properly reflects the issue. I found that if I simply moved /sites/all/themes/adaptivetheme to /tmp, then moved /sites/all/themes/adaptivetheme/adaptivetheme back into /sites/all/themes the update works and the nagging stops. I also found that I needed to go into Appearances, make a change, save, and then undo the change, for all of the settings to take proper effect. Note that I have made some minor changes to pixture_reloaded_color.css, pixture_reloaded_color.inc, and two of the .png files, so this may explain the need for the extra steps.

Cracked open a webmasters issue: #2233805: Update installs my project as a sub-folder of the project

Hi Jeff
First of all thanks for yout great theme. I am using you theme on 20 sites right now.
I although have troubles for updating the theme.
I have installed your complete theme with subdirectories adaptive_core, adaptive_admin and adaptive_subtheme.
and I have created a custom subtheme from version 7,31 call footheme with renamed directory, info filte etc.
Due to the issues mentioned above I removed admin, core and subtheme and did a clean instal of it. I didn't touch the footheme.
After clearing cache I still get the message that I have to update.
Do I even have to update the footheme with the new 7,32?
Please advise because update mails from 20 websites are quit annoying
I realy would apreciate your advise.

@youlikeit, technically speaking, no, you don't need to update your sub-theme, it will run perfectly fine without any changes.

@21 Thanks Jeff for your reply. Hmm but to stop update messages I have to update although my custom made subtheme?

Here's a "me 3".

Sure enough, there is 3.2, sitting as a subdirectory to 3.1.

I'm hosted on Pantheon, in case that matters.

If you made a sub-theme you may have left some lines at the end of the .info file that are causing notices to update after the base theme has already been updated. Removing these lines from your sub-theme.info file will stop the update messages.

eg.

; Information added by drupal.org packaging script on 2012-09-19
version = "7.x-3.0-rc1"
core = "7.x"
project = "footheme"
datestamp = "1348059849"

or

; Information added by drupal.org packaging script on 2012-07-31
version = "7.x-3.0-rc1"
core = "7.x"
project = "sky"
datestamp = "1343717266"

#24 did the trick!! Thanks Neil!

Using Pixture Reloaded 7.x-3.0 ... over AT ...
Did the update to AT 7.x-3.2 ... but visiting /admin/appearance shows that I still have AT 3.1 installed ... and I still get the warning that there is an update for AT ...
Did the update to AT 7.x-3.2 time and again ... same thing happens ...

Me 4... adaptive theme directory being installed inside the adaptive theme directory on two sites, and getting update eMails daily.

Shawn

There are at least two options you have that have previously been discussed - first a manual installation, and two check the version strings as per comment #24.

That is all I can personally do since I don't control the Drupal update system, I'm sorry about that but my hands are pretty tied here. Lets hope when I release the next version this magically fixes itself, fingers crossed.

Just notification that this issue is still a problem, three years later.

I used the Drupal update function within the website and it nested the new module inside of the old one, so drupal couldn't see it.

So, then I used filezilla to manually delete the entire folder and replaced it with the new release. In my case I was updating from 3.2 to 3.4.
The manual update put everything right and drupal could see it - update notification went away.

I am suddenly getting an outdated theme on virtually all the sites that have this theme - it says the current verision is 7.3.2 and it needs to be 7.3.4.

When I checked, the new version is stored in sites/all/themes/adaptivetheme/adaptivetheme.

Moving the site from a subfolder of itself into the main folder of "themes" fixes the issue and the request for an update.

I moved hosting company - possibly some setting that previously allowed the subfolder to be found and read, now doesn't allow it.

Same problem. #17 worked for me. Thank you.

#18 worked for me FYI! Thank you,