Re: Problem upgrading from 0.9.1

[Andrew vonderLuft]

demo.radiantcms.org refreshes its data on the hour with rake db:bootstrap using the Styled Blog option.  You can run this locally and then examine the data that way.   If you need more help with Radiant sites professionally, you can contact me at AVLUX support at sup...@avlux.net

Andrew vonderLuft

On Sunday, May 19, 2013 1:45:32 PM UTC-7, C Kiser wrote:

I upgraded from Radiant 0.9.1 to 1.1.1 this winter when all the security updates went out. The published material all worked fine but I never got the admin interface working again. Now I would like to start adding to my site again. Upgrading further, to 1.1.3, fixed the rake incompatibility that had been my previous problem. But I seem to have some data anomaly that is making my Articles (Archive) page gray out the "Add Child" button. I tried poking around in the radiant source code but am not seeing anything obvious at first glance. Since I don't have any non-core extensions installed, I am pretty sure this is just a data issue. Would it be possible to get a database dump from demo.radiantcms.org (in it's stock setup)? I am pretty sure I can spot the difference in the data more quickly than I can read through the source code. 

Thanks,

[Cynthia Kiser]

Quoting Andrew vonderLuft <avl...@gmail.com>:
> demo.radiantcms.org refreshes its data on the hour with rake db:bootstrap
> using the Styled Blog option. You can run this locally and then examine
> the data that way.

Thanks. I didn't realize that data refresh was distributed in the
stock Radiant distribution. I'll give that a try this evening.

[Jim Gay]

You'll actually need to include the radiant-site_templates-extension
in your project. I don't recall if that is in the default set or not,
but check your Gemfile for the reference and uncomment it if it is
commented out.

> --
>
> ---
> You received this message because you are subscribed to the Google Groups "Radiant CMS" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to radiantcms+...@googlegroups.com.
> For more options, visit https://groups.google.com/groups/opt_out.
>
>



--
Write intention revealing code #=> http://www.clean-ruby.com

Jim Gay
Saturn Flyer LLC
571-403-0338

[Cynthia Kiser]

Quoting Andrew vonderLuft <avl...@gmail.com>:
> demo.radiantcms.org refreshes its data on the hour with rake db:bootstrap
> using the Styled Blog option. You can run this locally and then examine
> the data that way. If you need more help with Radiant sites
> professionally, you can contact me at AVLUX support at sup...@avlux.net

Thanks for the help. The problem turned out to be in the file system,
not the data. To upgrade to Radiant 1.1.3, I committed everything to
version control and then just reran the 'radiant' command to
regenerate the site in the same directory. That mostly worked - except
that it did not copy new versions of the admin javascripts and css
into place - probably so as not to overwrite any customizations.

In case anyone else has similar upgrade issues, I figured this out by
creating a completely new radiant project and pointing it at my
existing database. Since that worked fine, I just did a brute-force
recursive diff of the directories for the new site and my upgraded
one. Once I copied the javascripts file from the new site into my
existing one, I could access my existing blog posts and can add a new
one.

Thanks again for everyone's help.

--
Cynthia N. Kiser