I am building my application in Codeigniter. It has a module where users create documents, which can be edited at a later time. How do I implement a 'history' of revisions, perhaps like a wiki ? Is it possible to embed a php wiki in a web app (twiki/dokuwiki)?
Consider embeding a wiki into your application so that you don't have to create your own wiki-like functionality from scratch. I know dooWikis enables you to do this without displaying any third-party branding or advertising on your site while still giving you control over who gets to make changes to the content.
Related
I have an umbraco based CMS site and I've been advised to use AMP for fast mobile performance. I have read the demo page from this gitHub link.
But I am not understanding how to set it in an already developed site. Do I need to change all tags according to AMP?
better not to mess with existing instead you build new AMP version of your site
(After doing a quick Google)
I don't think there's a an AMP-plugin for Umbraco yet, but that will probably be the way to go. I've been using the AMP-plugin for WordPress for a little while now and it made all posts on my site AMP-compatible without me having to do anything :)
Perhaps check with the Umbraco community whether there's an ETA on such a plugin for their platform?
You can have seperate AMP pages and google will handle the rest. I think that is the safest way to approach it, without having a plugin like they have for wordpress.
You can still enable the users to use the CMS functionality by creating custom data types for e.g. amp-img instead of img. The content editors will just have to be briefed on the basics of AMP.
References:
https://carolelogan.net/blog/amp-implementation-in-umbraco/
https://www.ampproject.org/docs/guides/discovery
I am trying to learn how to make a site with PyroCMS. I know it is similar to CodeIgniter, but I have not worked on either in the past. I was wondering if anyone could tell me the differences, as most sites talking about PyroCMS will inevitably mention CodeIgniter as an explanation for anything potentially confusing about PyroCMS, but as they are tutorials about Pyro, they will not explain how to program in CodeIgniter. What is frustrating about this is they will not go into many core differences between the two, either, so it's not as easy as looking up a CodeIgniter tutorial and changing a few things.
I was wondering if anyone could tell me the main differences to watch out for that would be relevant for these tutorials. For example, the folder structure seems to be similar, but CodeIgniter has an Applications folder, while Pyro probably has another folder that does the same thing, but the Pyro tutorials don't say what that similar folder is.
PyroCMS is a CMS build on CodeIgniter. PyroCMS is used by individuals, small & medium-sized businesses, and large organizations worldwide to easily create & build a variety of websites & web-enabled applications.
CodeIgniter is an Application Development Framework - a toolkit - for people who build web sites using PHP. Its goal is to enable you to develop projects much faster than you could if you were writing code from scratch, by providing a rich set of libraries for commonly needed tasks, as well as a simple interface and logical structure to access these libraries. CodeIgniter lets you creatively focus on your project by minimizing the amount of code needed for a given task.
UPDATE:
One good overview for PyroCMS you can read here
PyroCMS is built using modular MVC, which means (in short) that each part of the system is its own micro-instance of MVC. This allows the system to be more flexible and cleanly organized than other CMS platforms. PyroCMS describes itself as a simple, flexible, community driven content management system.” And because PyroCMS is powered by CodeIgniter (at least for a bit longer, while the team migrates over to a Laravel backend), it is easy to learn, understand, and own.
CodeIgniter (CI) is one of popular php framework,it is very help full whenever we need to build large websites using php.It has so many libraries,helpers and plugins.But, CodeIgniter is not everything. We will not find 'engine generator' that can build page self. Several frameworks have features like that. For example, they can create web page (that to do basic Create, Read, Update, and Delete operation) automatically. CodeIgniter doesn't do this.
But codeigniter is very useful to decrease our code maximally without loosing functionalists.
Okay. This is the main functionality of my site. Here goes:
People register. They upload a list of whatever ebooks, movies, tv shows they have. Other people who want them will just have to 'search' for an item and they will be provided with a contact form to contact a person that has what they want. Very much like pianofiles.com but this is for a local community.
Added features could be
*forming social groups by interest
*creating events
etc..
Is all this possible using Typo3?
If yes, then how should I use Typo3 for it? (Just a basic idea)
If not, what should i use to create something like this?
Check out the TER, a quick search revealed http://typo3.org/extensions/repository/view/community
You could realize your project with any well known CMS or PHP framework.
TYPO3 CMS, as I see it, has a strong emphasis on the editor backend. If you don't need that at all and don't have any prior experience, I'm not sure if it's the right tool for you - unless you want to get into TYPO3 anyway!
PS: For TYPO3 web apps, there will be the upcoming Framework http://flow.typo3.org, wich is in beta
I had an issues with some joomla api. The issue was that I was using the latest version of joomla and couldn't find where a joomla class, that was being called in my code, was derived . I searched the joomla api docs and found nothing relating to the class I was looking for.
I then stumbled across the refactoring change log for joomla and noticed that the function i was after had actually been moved from /libraries/joomla/form to libraries/cms/form.
Why would this be the case? There doesn't seem to be any reference to /libraries/cms in the api docs. How are we suppose to know that there are classes living there? Very confusing.
Since Joomla! 1.6 the code has been progressively split into the Joomla! CMS and the Joomla! Platform. You can see this separation in the github repository - a good place to also keep track of changes that are committed to both the CMS and the Platform. The simplest way is fork each repository and keep track of them.
As classes are updated they may be migrated to the /libraries/cms directory if they apply specifically to the CMS application (e.g. html forms are an application level function not a platform level).
I find the best place to hear about changes under discussion are in the respective Google Groups - Joomla! Platform Development and Joomla! CMS Development
[Edit]
Documentation of class's is the hardest thing to find for Joomla! CMS - there doesn't appear to be a current api listing for it, unlike the Platform API reference. Often it is just easier to read through the code.
It's also worth keeping a watch on the developer sub-site.
If you want to define excellence in CMS without coding, Joomla is the right option for you.Joomla the most preferred content management system among developers is an easy-to-use open source solution.If you want to define excellence in CMS without coding, Joomla is the right option for you. In this post, you will find few of its features that make the website development easy and most preferred option for developers.
I am new to open source Content Management System tools. I got a website using Joomla for content management. Now, I am just thinking to Umbraco or Dotnetnuke (any Asp.net based) frameworks to use. Will it be a complex to do this migration. Can you suggest pros and cons for this idea.
Any help is appreciated. Thanks !
For Umbraco ...
Most of your client-side code like HTML, CSS and JavaScript can just be copied straight over, but as expected it may require some fiddling.
As for the data, it might be worth looking into the CMSImport module for Umbraco. As long as you can convert the source data into one of the formats recognised by the module, you should be able to upload your content with ease. I've had no personal experience with this module, but should be worth a shot.
It really depends on the size of the site and the functionality requirements. For smaller sites, it may be as easy as implementing the skin based on the original design (or, if a custom design isn't needed, selecting a free or 3rd party skin) and then manually migrating the content. For really large sites, you should be able to write scripts to migrate the content. I'm not aware of any products that do this. You'll also probably need to select some modules to use for things like forms.