| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
| |
Ideally I would like to have the sidebars expand to show all their
contents, but I have not found a way to make this look nice. They should
also expand their container, so that the footer comes below the
sidebars. For now this seems like an acceptable solution.
|
| | |
|
| |
|
|
|
| |
- Module headings now go all the way out.
- Side body content is included like a module only if not empty.
|
| |
|
|
|
| |
- Wrap text in simple html.
- Assign sidebar position to categories.
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Run 'vagrant up' to bootstrap the environment. The first time you
do this, takes quite some time as it will download the base image,
and provision it for the dev environment.
Onse up you should be able to log in the the dev website by
pointing your web browser to localhost:4567. The first time you
will have to register a new user, and off you go.
Run 'vagrant halt' to stop the vm. Next time you restart it using
'vagrant up' it should boot a lot faster, since the provisioning is
already done.
Run 'vagrant destroy' to clean up the VM and reclaim any disk space
used by it. This will not remove the base image, only the instance
in this dev environment.
Notice: Due to a problem, the dev web server fails to start when
doing a 'vagrant up' after the initial provisioning. To overcome
this issue the following commands and you should be fine again:
vagrant ssh
sudo systemctl start rails
logout
Now wait a few seconds and the web server should respond again.
I'll try to fix this problem later.
requires vagrant and VirtualBox to work.
See http://www.vagrantup.com for instructions on how to install
vagrant for your system.
|
| | |
|
| | |
|
| |
|
|
| |
Also fixes DOM id of sidebar modules with spaces in their title.
|
| | |
|
| |
|
|
| |
Also strip out modules with empty bodies.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
There was some problems with the approach in the previous commits.
- render_collection (render @sidebar_modules in our case) requires
that all objects return the same partial path. Ours may not do that,
so we wrote our own `render_sidebar_modules`-helper.
- The way render_partial finds the correct path to the partial is
to append what's returned by to_partial_path with whatever root
the parent view is in. That would require duplication of the partials
under all the different engines namespaces. Our `render_sidebar_modules`
does it differently, and just looks up the partial according to the
root namespace. This means the sidebar_module code can move back under
the root application so we don't mess up the refinery namespaces.
- Finally found the proper way to link to a blog_post so that it
works from all namespaces. The correct way is:
refinery.blog_post_path(post)
This works in views (and presumably helpers,) but not in controllers
which is why we struggled with it before.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
Rewrite the _sidebar_module partial to render only one module,
and to not make any assumptions about the contents of a module.
(Except that it has a title and a body.)
Move the actual module logic into model classes, and use the
ActiveModel magic to have it find it's own partial. Now we
have the view logic for each module in it's own partial that
in turn renders as part of the _sidebar_module partial.
Only implementation this far is the blog-category module
listing the latest blog entries within each category.
|
| |
|
|
|
|
| |
I would like to just render the refinery/blog/index template for
this, but I did not find a way to do it, so I copied it instead. May
need to revisit this if upgrading to a new refinery or blog engine.
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
| |
Note to self, use model decorators to massage model data, but leave
the markup to the views where it belong.
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
Also did some code cleanup in
PagesControllerDecorator::populate_sidebars.
The controller will now populate left and right sidebars (only
left for now,) while the SidebarPostDecorator will provide the
markup for each post that is to be shown in a sidebar.
The plan is to further expand the system with other Sidebar-
Decorators, so each item can be rendered using the same in the
partial.
|
| | |
|
| |
|
|
|
|
|
|
|
| |
Run `rake dev:load_sample_data` to populate the database with
sample data. This creates the following:
- The categories [Nyheter, Intervjuer, Anmeldelser, Artikler]
- A "sample user" we can use as the author of posts.
- 5 blog posts in each category.
|
| | |
|
| | |
|
| |
|
|
|
| |
List blog categories and 10 most resent posts in each category in
the left sidebar.
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
| |
Enable all the standard engines:
- blog
- inquiries
- search
- page-images
- videos
|
| |
|
|
|
| |
Now copies the example refinery core config to the right place. And don't
bomb if database.yml already exist.
|
| |
|
|
|
|
|
|
| |
Require the scripts in config/deploy directory so they will hook
into the deploy process.
Fixed deploy:refinery:setup recipe, now produces a valid config
and puts it in the right spot.
|
| | |
|
| |
|
|
|
| |
Rails -> 3.2.13
RefineryCMS -> 2.0.10
|
