I'm trying to start building a whole application using phpBB3 user system as a base using CodeIgniter framework. However before starting I would like to hear a piece of advice from any phpBB3 Developer out there.
I've been developing for Wordpress and Drupal. But recently I decided I would build up something fit to my needs instead of using a premade application.
The application is going to include:
Article System
Video Streaming
Wiki
User editable Profiles
and much more
To any phpBB3 Developer :
Where to start?
Any recommendation you could give me?
Any tips?
I've only used phpBB3 as a forum system, but you should definitely check out the phpBB Development Wiki, particularly the API section.
It has all sorts of neat things, like how to add custom pages and use phpBB's permission system.
Related
I was wondering if anyone could point me towards some resources about developing systems that incorporate VB user system? My client requested me to develop a PHP system for content management that uses the VB user system for commenting, logging in, etc. Any resources would be appreciated
Thanks,
S
vBulletin offers a "Data Manager".
With this you can do the most things like add users, posts, threads and a lot more.
Read the documentation for more:
https://www.vbulletin.com/docs/html/data_manager_programming
To login into vBulletin from a non vB Page is a bit more difficult.
You need to change the current directory to your forum path with chdir('/home/forum/') and then include/require the globlal.php
A full example can you find here http://www.vbulletin.org/forum/showthread.php?t=108026 for vB 3.x.
But for vBulletin 4.x it should be similar.
I'm working on a web application in Codeigniter. I'd like to integrate the functionality of my application with a CMS so that site admins can easily update the site (about pages, blog, etc). Is this easily done with PyroCMS or another Codeigniter-based CMS? Will I need to drastically restructure my existing app?
From my own experience integrating an app inside Expression Engine I can say that a CMS changes the way you usually work with CI. So be prepared to make some adjustments. Every CMS will come with it's perks and differences. It shouldn't be a big problem though.
If you want to use PyroCms take a look at this doc first:
http://www.pyrocms.com/docs/2.0/developers/creating-custom-modules
If you're looking for alternatives, there are a lot. It seems almost everyone working with CI has made it's own.
Here are a few:
http://www.ionizecms.com/
http://www.halogy.com/
http://codefight.org/
http://www.getfuelcms.com/
Also make sure you check out CI Bonfire, it's not a CMS but does help you when you start up a new project with a basic admin wrapper, which is sometimes more useful than a CMS:
http://cibonfire.com/
This was answered a year ago and answered well, but my support guy has forwarded me a few emails from users asking about this page.
When people talk about Content Management Systems they often suddenly get the idea of rigid backends where you applications have to follow specific rules. While PyroCMS certainly has a few conventions you are free to build your modules just like they are a CodeIgniter application, on the frontend or the backend.
If you want to use Models, Controllers, Views, REST API's, SOAP, whatever the hell, then you can do that.
But, we also offer some awesome tools to make building modules CRAZY-fast. Hate writing CRUD? Well don't bother. Using the Streams API you can leverage the build in "Custom Data" system we use to rock out chunks of interface for you.
Using PyroCMS for your application is certainly not "hacking it into a CMS", this is the exact use-case it was built for.
If you have an existing application, while you can't "put PyroCMS into your app" you can certainly convert your application to a module easy enough.
The simplest way of doing it is to write your models around the CMS' database. Host the CMS at a subdomain with authentication for your admins. (admin.mysite.com) or something and then use the same database to power your front-end for your site.
Is it the best approach? Probably not.
Will it work? Yes.
You will probably find it hard to expand vertically & add new features if you're relying on a 3rd party CMS for data entry & backend.
I asked this very same question on PHP forum to which I got no response.
In terms of:
time spent on programming
performance of blog
flexibility
would it make sense to build a blog on codeigniter from scratch or integrate an existing WordPress blogging software with the codeigniter site? Reason why I ask because if you want to only have one log in and have admin approval based on admin from site, you come across problems when trying to integrate blogging software which has its own tables for things. Importantly, what if you want a clean database design not be influenced by external blogging software, generating its own tables? Modifying existing blogging software can be just as time consume as building one custom for your site, I believe.
In terms of the three criteria above, which would you believe is more effective approach?
THanks for response.
I think their are plenty of blog/CMS solutions available, already built on codeigniter, that you'd be better off staying away from mixing platforms, which can get messy and create a big headache down the road if you don't properly document your steps of integration.
A few to get you looking
PyroCMS - basically the defacto standard for Free(Beer and Speach) CMS for CI
BLogmer - A blogging platform written on CI that I found after a quick google search
I have a full CMS and I want to integrate it with phpbb.
Basically I want when user registers -> registers with phpbb and same with login.
Is there any good tutorial or something that can help me?
Depending on the CMS you are using, you will need what phpBB team calls Bridges. You have several existing, and the most powerful is clearly the Drupal Bridge
http://www.forum-software.org/phpbb3/review
I have a web application that needs to be built using PHP/MySQL. The application will require documents to be generated from data in the MySQL database. Such documents will be printed and/or emailed and user will be prompted to run a daily print/email job based on business logic.
This application functionality needs to be made available to individual users such that they can upload data, have the system prompt them as to whether letters/emails are to be generated. The site also needs to be able to support a bulletin board, online live training events and will have admin area as well.
Question: Should a hybrid solution be developed such that the data management (upload functionality, and letter production) be a separate part of the site that authenticated Joomla users can access? That is, the document management functionality would exist separately from Joomla, but be called from within it via a link in the Joomla sitemap. Alternatively, should custom modules be developed from within Joomla to accomodate the document management functionality?
Thanks so much for your input!!
Joomla could do the job for you but based on the amount of things you need that differ from a normal Joomla site I would use a framework to build from instead of a CMS. I say this because it sounds like you need a lot more than just a CMS and it can be more work if you try making Joomla do things it wasn't designed to do. In my opinion Joomla is for "web sites" and not as much for "web apps". Of course those terms have overlap but it sounds like you would be better off with a Framework to go off of instead of working around Joomla to get what you want. However if the site is already done in Joomla it may be less work just to make a Joomla add-on.
Since you have to use PHP I would definitely recommend CakePHP for your framework. As for an integrated forum try looking at the links in this post. If that doesn't work for you, try out Vanilla forums (vanillaforums.org) which are very clean and may be easier to integrate into CakePHP than some of the other PHP forums.
If you decide to use CakePHP, check out Cake Forge to see if you can find anything there to make your life even easier.
If you were to use Joomla, the upload functionality and letter production would be written as a custom component. You can write the component to make sure that the current user is authenticated before generating the documents. I would not develop this as a separate application alongside Joomla; it would be easier to write it as a component.
Many forums and forum bridges are available for Joomla, so that would be something you wouldn't have to write.
I'm not sure what kind of live event support you're looking for.