Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 3 years ago.
Improve this question
Im beginning a new project with Laravel 4 / 5 (done this many times).
I dont want to re-write the wheel setting up admin interfaces and user authentication.
Is it wise to use something like OctoberCMS and pull it part to my own ends?
Why I would do this:
I want extensive CMS functionality
I want a nice user interface
I dont want to code all that!
I have dabbled with the october CMS, and it's really great (as a cms) for someone like a front end dev (rather than say, a generic client who wants to just update content).
A lot of work has been put into the CMS, and to use it effectively you will be extending the October CMS which means doing things the "October way" assuming you want to tie most of your added functionality into some sort of user interface.
If you are ok with learning the ins and outs of October - then it seems like in the long run it will be of benefit.
If you don't go with October - there aren't many alternatives ([packages] which I have come across) which provide a simple foundation and have been updated recently - having said that the core of wardrobe might be something to look into: https://github.com/wardrobecms/core
As for roles/auth - take a look at Entrust (https://github.com/Zizaco/entrust) and Confide - I have used them together in the past and found them functional and easy to use.
(I have no affiliation with any of the packages mentioned above)
Related
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 12 months ago.
Improve this question
I have a admin panel made with Codeigniter 3.1.6 version. I searched it but i found different opinions about it. Can i upgrade it to 4.1.9? I have site settings, image uploading, mail sending and some different things in my project. (iziToast, sweetalert, toggle button)
I believe this is a big endeavor but nonetheless - this should give you some structure and pointers - Upgrading CodeIgniter 3 to CodeIgniter 4
While most is generally to Filetype (Model, View or Controller) and specific upgrade and/or omissions of libraries and in few areas extensive changes might be needed in your code.
Most of the changes must be from Models as more of CRUD Functionality is built-in available, while Configuration Files is completely different than CodeIgniter 3. I believe part by part some areas might be tricky.
Wishing success ahead with new features and Built in ORM.
P.S. - Myself am beginner in CodeIgniter 4 only.
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
We don’t allow questions seeking recommendations for books, tools, software libraries, and more. You can edit the question so it can be answered with facts and citations.
Closed 7 years ago.
Improve this question
I am writing a Laravel application. this application needs to a CMS.
my application have something like user membership,newsletter emails, authentication,advanced searches etc, depend on posts.
a CMS can not handle my application alone.
I need to an extendable CMS that resolves my requests.
I saw October CMS gallery and I think it is for blog or simple sites not an extendable application.
What extendable CMS or package (in Laravel) can resolve my requests?
I think all you can do it with OctoberCMS, it is not pure CMS, it is developer first CMS, you can extends this as you want, there is no restriction in extending this, as per my opinion, all things you can do with laravel is possible with OctoberCMS.
Please double check its features https://octobercms.com/features
what you can do is you can keep Laravel and OctoberCMS in one project, for CMS part use OctoberCMS.
October is pretty much amazing. I think you can do anything with it. When I saw their website the first time on a recommendation of a friend I also saw it as a simple CMS - but look at the documentation- and resources-page: You can create your own plugins, it has a very intricate and easy to understand databse-handling that also manages complicated relationships like "many to many polymorphic" and there is an easy way to create backend-pages that contain forms with those relations. In my opinion its really amazingly thought through and it can serve as CMS-part for almost anything.
i heard talking about Platform by cartalyst but i never try it.
take look if you want and i think it responds to your needs.
https://cartalyst.com/manual/platform/4.0
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 8 years ago.
Improve this question
I just started to investigate Orchard for the 5:th time, and I thought that I might want to give it a fair chance.. however.. there is one think that me and my collegues simply cant get our heads around.. why is the UI so "techy"?.. For instance Umbraco has a very clean and simple Admin UI thats mostly understandable by anyone (even "none tech" persons)..
So my question is basically, is there something that we are missing?.. is there any user advantage to the Orchard Dashboard UI over the Umbraco UI for instance, or is there any module thats a "must have" to make the UI a bit more familiar?
Every time i have a new orchard instance, i always install the module Theme Editor
https://gallery.orchardproject.net/List/Modules/Orchard.Module.M33.SystemEditor
This module allows you to edit Views, JS, CSS inside of the cms itself. This probably complicates the UI even more however.
To answer your question, there is nothing to my knowledge to make the UI easier to adapt to. However if you spend the time to get to learn it then you realize there are a lot of very powerful things you can do with it and it is a fantastic example of MVC that is at your fingertips to modify to your hearts content.
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 9 years ago.
Improve this question
So I am starting an internship this week, I will be working on making some changes to an existing Oracle Apex web app which they use for tracking and metrics. In particular, they don't have very granular authorization set up, meaning that either you have full control or you don't. They want me to come up with something to set up access for non-tech users like the business, for example, and limit their rights to the system.
How hard is apex to work with? I looked into it a bit, it does seem fairly straightforward, but is there more to it that I am not aware of? Also, I am a little surprised that there is no built in functionality to let you set up complex permissions?
I've been working in Apex since August now, and did 4 years of Oracle Forms before this, so PL/SQL wasn't an issue for me. HTML and Javascript i also knew, just not as in-depth, but i believe i've picked up nicely so far.
What i'm doing at the moment is migrating a bunch of old Oracle Forms to Apex. So far my experience is that it can be very easy and fast to pump out the basics, but making your pages more dynamical or user-friendly can eat away some time. Still, the framework is very solid, save for some niggles. For example, they have a javascript api, which handles a lot like jquery. I can mostly get done what i want to, and i think the most time i've "wasted" so far, has been getting javascript code to work the way i want it.
Recently i've also been implementing some authorisation, and i must say it isn't really that hard! You can provide some authorisation schemes, and simply apply those to pages, regions or items. I of course don't know what you really mean with 'complex' permissions ;) There is always the possibility of using the APIs and do manual calls to verify authorisation.
If you're really totally new, then simply head over to apex.oracle.com, and take the 2-day developer guide to get a quick feel for the environment. You'll have to request a workspace, can do the exercises, and play around a bit.
We were looking at apex a year ago. And canceled. It's easy to make standard things, but it's not convenient to develop something specific. May be, we were looking not very properly, indeed.
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 6 years ago.
Improve this question
There are a million and one CMS' that do a good job but the interface and usability of it let the entire system down (like a lot of websites out there).
Whenever I need to develop a bespoke system for content management I always try and draw on my past experiences and those of my clients to work out what works well and what doesn't. So each time I do one there is a similarity to the last but with some extra tweaking to make it that much better.
So the question is what CMS interface / features have you found a pleasure to work with and why?
Note: This could be editing pages, products, sitemaps, just about anything you needed to manage through a CMS
I personally think inline-editing is a massive speed boost for clients and developers.
Drupal 6's draggable menu reordering is a great feature. It is faster and more intuitive than the weight system from Drupal 5 and the up/down arrows I have seen elsewhere.
I agree with jchrista, drag-and-drop is very nice. This is the feature that initially drew me to Sitefinity. There is an online demo of this here.
I hate InterWoven (just because I find it slow and non intuitive--subjective..), but it has a nice WorkFlow setting that enables you to control the versions you have on the server between what you have been working on and what should be deployed.
Also a good (go back to before the screw up) productivity tools
MOSS has lots of interesting features that are supposed to do the same thing also, which I will look forward to test as we move towards that platform.