Forum: Ruby on Rails [ANN] Showcase On Rails CMS v0.1

Announcement (2017-05-07): www.ruby-forum.com is now read-only since I unfortunately do not have the time to support and maintain the forum any more. Please see rubyonrails.org/community and ruby-lang.org/en/community for other Rails- und Ruby-related community platforms.
4bd34a2216dc8bdbf1f017f64e4d59e8?d=identicon&s=25 Kyle Maxwell (Guest)
on 2006-02-23 02:29
(Received via mailing list)
I built out a simple CMS for websites that rely heavily on portfolios.
This covers graphic and web designers in particular, but also other
people with stuff to show off.  It's really easy to customize
progressively, so that some people will only modify CSS, but others
will dig deeper into Javascript behaviors and the Rails view code.

Check it out at http://showcase.kylemaxwell.com/
SVN co at http://svn.kylemaxwell.com/showcase/
then rake migrate up a fresh database, and you're good to go (/me
waves hand a la Taco Bell commercial)

Features:
- 100% semantic XHTML
- Built on Ruby on Rails
- AJAXified administration
- Revision management
- Textile/Markdown-driven editing
- File uploads and image thumbnailing

As usual, feedback is great; patches are great.aculo.us!

--
Kyle Maxwell
Chief Technologist
E Factor Media // FN Interactive
kyle@efactormedia.com
1-866-263-3261
4005a47a8f2ceee49670b920593c1d52?d=identicon&s=25 Ben Munat (Guest)
on 2006-02-23 07:46
(Received via mailing list)
Hey Kyle... I checked it out, set up the db, and ran the app. The admin
screens seem to
work fine, but whenever I try to go to a "regular" page I get this
error:

  NoMethodError in Showcase#page

Showing app/views/showcase/page.mab where line #0 raised:

(eval):11:in `instance_eval': You have a nil object when you didn't
expect it!
The error occured while evaluating nil.title

Extracted source (around line #0):

1: div.navigation do
2:   h4 { span @website.pages_title }
3:   ul do

thanks

b

PS: I see you're using markaby (COOL!)... do I need to do some oher
installation stuff for
that?
F15fdc7cb2e911b3808837f2be244add?d=identicon&s=25 Adam Denenberg (Guest)
on 2006-02-23 15:04
(Received via mailing list)
Mysql error after rake migrate:

Mysql::Error: You have an error in your SQL syntax.  Check the manual
that
corresponds to your MySQL server version for the right syntax to use
near
'ENGINE=InnoDB' at line 1: CREATE TABLE websites (`id` int(11) DEFAULT
NULL
auto_increment PRIMARY KEY, `keyword` varchar(255), `title` text,
`subtitle`
text, `stylesheet` text, `behavior` text, `footer` text, `pages_title`
text,
`categories_title` text, `updated_at` datetime) ENGINE=InnoDB

adam
4bd34a2216dc8bdbf1f017f64e4d59e8?d=identicon&s=25 Kyle Maxwell (Guest)
on 2006-02-23 18:46
(Received via mailing list)
Ok, let me check and see what's going on...
4bd34a2216dc8bdbf1f017f64e4d59e8?d=identicon&s=25 Kyle Maxwell (Guest)
on 2006-02-23 18:55
(Received via mailing list)
On 2/23/06, Adam Denenberg <straightflush@gmail.com> wrote:
>
> > (eval):11:in `instance_eval': You have a nil object when you didn't expect
> >
> > > progressively, so that some people will only modify CSS, but others
> > > - AJAXified administration
> > > kyle@efactormedia.com
> > _______________________________________________
>
>
>

That's a pretty standard migration.  Are you having trouble with other
migrations?  What version of Rails, mysql are you using?

--
Kyle Maxwell
Chief Technologist
E Factor Media // FN Interactive
kyle@efactormedia.com
1-866-263-3261
4bd34a2216dc8bdbf1f017f64e4d59e8?d=identicon&s=25 Kyle Maxwell (Guest)
on 2006-02-23 19:04
(Received via mailing list)
On 2/22/06, Ben Munat <bent@munat.com> wrote:
> Extracted source (around line #0):
> that?
> > then rake migrate up a fresh database, and you're good to go (/me
> > As usual, feedback is great; patches are great.aculo.us!
> >
> > _______________________________________________
> > Rails mailing list
> > Rails@lists.rubyonrails.org
> > http://lists.rubyonrails.org/mailman/listinfo/rails
> _______________________________________________
> Rails mailing list
> Rails@lists.rubyonrails.org
> http://lists.rubyonrails.org/mailman/listinfo/rails
>

That's actually how a certain 404 error displays.  I just replaced it
with an actual 404 error page (so svn up).  The question is now: why
are you getting 404's? Perhaps it's a bug in the cache sweeper, or
maybe you went to a page you had previously deleted, but was present
in your history?

--
Kyle Maxwell
Chief Technologist
E Factor Media // FN Interactive
kyle@efactormedia.com
1-866-263-3261
F15fdc7cb2e911b3808837f2be244add?d=identicon&s=25 Adam Denenberg (Guest)
on 2006-02-23 20:17
(Received via mailing list)
[root]# rails --version
Rails 1.0.0

[root]# mysqladmin -V
mysqladmin  Ver 8.40 Distrib 4.0.13, for pc-linux on i686


-adam
67d3880bbfaafdb2a2108b7c9a64df47?d=identicon&s=25 Adrian Madrid (Guest)
on 2006-02-23 20:26
(Received via mailing list)
Kyle,

Your demo looks great but I haven't been able to run the code in my
Site5
account. I have been able to do the migrations so I know the DBs are up
(checked with phpMyAdmin). But I can't get anything but a white screen.
No
activity on the rails' logs but this is what I get from Apache:

[Thu Feb 23 14:07:18 2006] [warn] FastCGI: (dynamic) server
"/home/cmsaem/public_html/dispatch.fcgi" has failed to remain running
for 30 seconds given 3 attempts, its restart interval has been backed
off to 600 seconds
[Thu Feb 23 14:02:18 2006] [warn] FastCGI: (dynamic) server
"/home/cmsaem/public_html/dispatch.fcgi" has failed to remain running
for 30 seconds given 3 attempts, its restart interval has been backed
off to 600 seconds
[Thu Feb 23 14:02:18 2006] [warn] FastCGI: (dynamic) server
"/home/cmsaem/public_html/dispatch.fcgi" (pid 29927) terminated by
calling exit with status '1'
[Thu Feb 23 14:02:18 2006] [warn] FastCGI: (dynamic) server
"/home/cmsaem/public_html/dispatch.fcgi" (uid 33344, gid 33347)
restarted (pid 29927)
[Thu Feb 23 14:02:18 2006] [warn] FastCGI: (dynamic) server
"/home/cmsaem/public_html/dispatch.fcgi" has failed to remain running
for 30 seconds given 3 attempts, its restart interval has been backed
off to 600 seconds
[Thu Feb 23 13:57:18 2006] [warn] FastCGI: (dynamic) server
"/home/cmsaem/public_html/dispatch.fcgi" has failed to remain running
for 30 seconds given 3 attempts, its restart interval has been backed
off to 600 seconds

 Any ideas?

Thanks,


Adrian Madrid
4bd34a2216dc8bdbf1f017f64e4d59e8?d=identicon&s=25 Kyle Maxwell (Guest)
on 2006-02-23 22:28
(Received via mailing list)
On 2/23/06, Adrian Madrid <aemadrid@gmail.com> wrote:
> been backed off to 600 seconds
> "/home/cmsaem/public_html/dispatch.fcgi" (uid 33344, gid
> been backed off to 600 seconds
>
> > then rake migrate up a fresh database, and you're good to go (/me
> > As usual, feedback is great; patches are great.aculo.us!
> > Rails@lists.rubyonrails.org
> Rails mailing list
> Rails@lists.rubyonrails.org
> http://lists.rubyonrails.org/mailman/listinfo/rails
>
>
>

Can you run ./dispatch.fcgi directly?  This smells like a permissions
or shebang issue.

--
Kyle Maxwell
Chief Technologist
E Factor Media // FN Interactive
kyle@efactormedia.com
1-866-263-3261
67d3880bbfaafdb2a2108b7c9a64df47?d=identicon&s=25 Adrian Madrid (Guest)
on 2006-02-23 22:52
(Received via mailing list)
Kyle,

thanks for the pointer. It was a shebang issue. One bug I found though
is
that if you run in development mode the migration creates a bunch of
empty
records (Rails 1.0.0, MySQL 4.1.14) but if I force it to run in
production
there is data in those rows. Also, in development or production when
going
to the site now I get a 'Please create a page' message but I didn't know
where to go to do that until I looked into the production DB in the
pages
table content. Now when I go into /account I can't login with
admin/12345.
It comes back to the same page with no errors or any kind of message.
You
can check it out here (I will leave it open for a while):

http://cms.aemadrid.com/account/login

Hope it helps,


Adrian Madrid
67d3880bbfaafdb2a2108b7c9a64df47?d=identicon&s=25 Adrian Madrid (Guest)
on 2006-02-23 23:56
(Received via mailing list)
Kyle,

I fixed most of my problems by moving the data from the production DB to
the
development DB manually. Then I was able to see the instructions on the
homepage and actually login. the only thing I see missing is that it
looks
weird on Firefox/Win (all the edit/delete/etc links mess up the ) but
that
is just cosmetic.

Hope this helps,


AEM
4bd34a2216dc8bdbf1f017f64e4d59e8?d=identicon&s=25 Kyle Maxwell (Guest)
on 2006-02-24 02:18
(Received via mailing list)
Thanks Adrian, I'll look into the database issue.  I've also been
meaning to redo the css for the account templates.  It's kinda on the
back burner tho.  I've been figuring that many/most users will
customize and rebrand it.

-Kyle
67d3880bbfaafdb2a2108b7c9a64df47?d=identicon&s=25 Adrian Madrid (Guest)
on 2006-02-24 04:56
(Received via mailing list)
Kyle,

Thanks to you. I guess you are right about the CSS. I would personally
change the CSS and even the layout.

Thanks again,

AEM
This topic is locked and can not be replied to.