Free CMS for RapidWeaver!


(...) #21

This is what was confusing me. PHP includes I understand and they are simple enough. That simple “php include” line was not going to get WP to work with RW in my mind. Thanks for clearing that up.

I am working on Bludit CMS and I might add it into RW. So far with this project I have not found a reason for RW other than to build a theme style with.

(Bob Afifi) #22

Hi Flash!
So just to double-check, you were able to get the “Hello World” biz to work?

(steve bee) #23

But that’s my point. If you’re going to use it for the backend, being that it has many frontends, why make life more complicated than it needs to be, why not use it for the frontend too, instead of RW?

(Bob Afifi) #24

Hi Steve,
Because this is not about making a WordPress site - it’s about adding CMS functionality to a RW site (like Pulse CMS, Total CMS etc). You could go direct to MySQL and not use WordPress, but the advantage of using WordPress - especially for clients - is the user interface. WordPress login/pass, GUI and version control is the reason I chose it over just going direct to MySQL. Hope that helps.

(Bob Afifi) #25

That’s correct - to connect and retrieve data from WordPress’ MySQL database you need a script. Here you go!

<?php $mysqli = new mysqli("localhost", "username", "password", "database"); /* check connection */ if (mysqli_connect_errno()) { printf("Connect failed: %s\n", mysqli_connect_error()); exit(); } /* Change wp_posts and ID to match your DB */ $query = "SELECT * FROM wp_posts WHERE ID=5 "; if ($result = $mysqli->query($query)) { while ($row = $result->fetch_row()) { printf($row[4]); } /* free result set */ $result->close(); } /* close connection */ $mysqli->close(); ?>

(steve bee) #26

Well, it still all seems to me to be a case of taking the long way round. If WordPress didn’t have a front end, I’d get it, but it does, so integrating it in to RW seems pointless to me: just build the site in WordPress!

But good luck all the same.

(Bob Afifi) #27

Hi Steve,
The problem is RW is not a CMS, which is the reason why there’s all these CMS stacks floating around. People like making websites in RW but then are confronted with the editing problem once the site is published - either when they’re not on their computer or if the site was for a client and the client wants to make an edit (again for example, change prices in a menu). That’s where the CMS functionality comes in. For a full blown CMS, RW would not be my first choice, but for sites that I have made for clients in RW that have only a few pages that may need periodic editing, it makes sense either to use a CMS stack or roll your own like I did. Cheers!

(steve bee) #28

I’ve loads of sites built for clients in RW that have editable sections, editable browser side by the clients. There are a ton of options out there: My most used is Armadillo with it’s solo content and page creation, next is Sentry if it’s just a few bits here and there. If I had a client that needed the level of editing that Wordpress allows, I’d use Wordpress! I’m just failing to see the point of building in RW then embedding WP content.

But, as I say, good luck.

(Bob Afifi) #29

OK Steve, you win. You like to use a CMS stack ($), I don’t.

(steve bee) #30

It really isn’t a case of trying to win, I just don’t get why your embedding WordPress content in a rw site.

(Bob Afifi) #31

I know you don’t get it and for that I’m sorry. I’ve tried to explain the rationale as best I can:

  • You don’t have to use WordPress, but it’s login/pass, GUI and version control are the reasons I do.
  • No licenses, subscriptions or conflicts with other stacks.
  • It’s free.

(steve bee) #32

But why not just build a Wordpress site? Why bother at all with RW???

(Bob Afifi) #33

OK, let’s try a different approach -
I checked out your bicycles site and your portfolio.
Now lets pretend you don’t have a CMS stack and furthermore there isn’t a CMS stack available.
All your clients start emailing you saying they want to change this or that.
What are you going to do? The sites are ready paid for. Are you going to rebuild all of them in WordPress or some other CMS for free? Maybe there’s another way, and there is. It’s called includes.

(steve bee) #34

Erm, yes.

If a client asked me to build a static site, then further down the line asked for it to be converted to a CMS, if no CMS existed for RW, yes, I’d rebuild it in WP if that were the CMS I’d chosen to use.

I mean, I’ve got to rebuild it anyway, so if the CMS system I were going to use had a fully integrated front end, I’d use it, especially given the fact it’s free, which seems to figure high on your list of requirements.

You seem to think I’m taking a confrontational view on this, but I’m really not, I just can not understand why you would go to the trouble of using the WP backend to drop content into a RW frontend, when WP has it’s own perfectly good front end.

(Bob Afifi) #35

Sorry Steve, apparently my command of the English language isn’t as good as I thought it was. Perhaps Gary or Greg can explain this better than I can.

(steve bee) #36


Blah blah blah.

(Brandon Scott Corlett) #37

I have been watching this thread and finally have a moment to throw in my 2 cents.

First things first, I really appreciate the sharing of technique. I know that one of the main reasons people use RapidWeaver is so that they are not required to code. This is exactly why I started using it. However, now that I am a developer as well as a designer I greatly value more technical conversations.

That being said, I think it is important to note that this solution will not be practical for the majority of users. Developers like @joeworkman have spent a tremendous about of time providing amazing solutions which are far simpler to use in a RW environment and require zero database setup.

Something like mySQL may seem simple enough to some of us, but lets also remember that for many users they haven’t even heard of FTP until they open RW for the first time.

I would also caution fragmenting your system architecture by splitting between RW and Wordpress. I know some people use WP specifically for managing a blog that is imported into RW. Although this is “free” and open source solution, if you are self hosting, you will then have to worry about all the maintenance that comes along with using WP.

Yes, WP is used on over 25% of websites in the public DNS. However, this doesn’t say how many sites have actually been completed, are receiving traffic, or still functional. One automatic update and any of your themes and/or plugins can break your site. Also, not updating your WP version, themes, and plugins is never a good idea with WP.

WP is the perfect platform to use if you wish to be an easy target for hackers. I use a Linux distro called Kali and it comes with a dozen or so tools for penetration testing WP sites. One the tools is called wpScan. All I have to do is put in a URL of a WP site and it will show me all of the vulnerabilities for that WP version, themes, and plugins. It then provides a convenient link to where I can learn all about the vulnerability and how it can be exploited. All of this has provided many businesses with the opportunity to make a ridiculous amount of money maintaining, troubleshooting, an recovering WP sites.

Lastly, before I move on for a bit, WP can only be “free” because they have highly inflated pricing for their hosted plans. It is not fair to compare this business model to that of Realmac/RapidWeave. Realmac does not have a subscription service that is priced any where as high as WP nor do they have as large of audience. Maybe this will change in the future.

In conclusion, I think conversations about code should be highly encouraged within the community. Along with that we should remember that code is not for everyone. Perhaps we could have a Code Junkie category added to this forum. Also, if anyone is using WP or plans to use WP they should also plan to invest the time to learn how to secure and maintain a WP site.



(Greg Schneck) #38

Not so much a “Code Junkie” forum… but more a “for those who want to venture outside the RW box.” I was handed a 1500 page RW site to maintain and obviously I’m not going to convert it to anything else. Yet, why shouldn’t I be allowed to “think outside the RW box” a bit when I want to do things like using includes, or free scripts, etc.? Surely there are other users out there who would want to learn more about htaccess, php, flat file or SQL databases, css, etc. Yet, the worry seems to be about confusing the novice… For example, I cringe when I think of all the RW users out there who have never once actually looked the files on their webspace. Who have never really looked at what’s in the “common” folder, etc. I guess it’s just me… but I enjoy learning things…

(Bob Afifi) #39

Thanks Brandon!
Regarding the security issues of WordPress, most people use shared hosting. My hosting company is very vigilant about updates - not only Core but plugins and themes as well. You can always add it to your functions.php if that’s not the case.

add_filter( ‘auto_update_plugin’, ‘__return_true’ );
add_filter( ‘auto_update_theme’, ‘__return_true’ );

Also, I’m just using WordPress for the back end, so noindex.
<meta name=“robots” content=“noindex”>

As for whether or not this CMS will be useful to RW users, don’t know. I know I had had enough of CMS stacks that didn’t work for me. I can say it’s doing what I need for my sites (and I’m not out $297).

Thanks again!

(Jan Fuellemann) #40

I am using the standard-free-plan wordpress blog just for some clients to enter blog entries. And the WordPress stack to display them on the RapidWeaver site.

About not using WP for everything: RapidWeaver is much nicer and more powerful and faster to build my sites with. It is a tool I like to use. So if I have the chance to use RW and import blog posts from WP - then I go this way.