I am new to opencart, and I am confused about the terminology between extension and module in opencart, could anyone explain to me?
Extensions: are used to give the additional functionality to the CMS
In Opencart, You have the extensions like payment, modules, totals etc.
Modules : this is the special type of extensions which is used to show the information at the front store or adding the functionality that cannot fit into other extensions types
read this article for more information
http://www.inmotionhosting.com/support/edu/opencart/admin-tools/what-are-opencart-extensions-and-modules
For Example:
Payment extensions : All payment extension have only one work to process the payment so it is further categorized as payment extensions.
and second thing all payment gateways should be list at checkout page so Opencart makes a special category for them same for total extensions
Modules: We cannot say what one module can do If you want to show the user just welcome message you can make the module for it and add it to any layout
Modules: blocks of HTML that have their own config in Extensions > Modules and can be applied to Layout Templates to appear on the left/right/top/bottom of the page. The category left nav is a module.
Extensions: zip files containing an /upload folder which contains files to be uploaded to the web root of your site and can include, new files, new themes, new modules and vQmods. Extensions can add pretty much any functionality to the store and often have an area in the admin for settings and often but not always make changes to the front-end of the store.
More info here:
http://www.antropy.co.uk/blog/what-is-the-difference-between-modules-and-extensions-in-opencar/
Extensions are add-on programs that provide extra functionality to your website.
Modules are boxes of information on your site that help the customer make their purchase. These do not provide extra functionality to your website but are intended to display information. Some modules are included by default, such as Account, Affiliate, Bestsellers, Featured, Specials, etc.
I hope this helps, look at this link for some more extensions.
Module is extention. Payment and Shiping and other is extentions to.
The contrast amongst modules and augmentations in Opencart are:
Modules: A more lightweight and adaptable expansion utilized for page rendering is a module. Modules are utilized for little bits of the page that are by and large less perplexing and ready to be seen crosswise over various segments. Some of the time modules are connected to a segment, for example, the centre most recent news module.
Augmentations: Components, dialects, modules, module and formats are altogether known as Extensions.
Related
I would like to do a project with TYPO3 v10 I'm new with this CMS and I need to create different templates for different pages but I don't understand which code I need to change.
I already install a sitepackage from this site https://www.sitepackagebuilder.com/
It work well but I need to create my own templates and I want to edit the content of my templates in the back end administration like in the picture.
I hope I'm clear
thanks for help :)
I am not sure if there is a misconception in the question or if I have interpreted incorrectly. In any case, I hope this helps:
It is important to differentiate between content + template in TYPO3:
content
In the screenshot posted in the question, you see the TYPO3 backend, which is a view for editing content, administration etc. There you see the page module is opened in the left column (1), you see the page tree in the middle column (2) and the page layout for editing content on the selected page in the right column (3). Here, you can insert and edit the content, that will be displayed on a page.
Template
In TYPO3, the template is what makes up the automatically generated parts of the page such as header, footer, menu, breadcrumb etc.
It work well but I need to create my own templates and I want to edit the content of my templates in the back end administration like in the picture.
Editing the template in the backend with a Wysiwyg ("what you see is what you get") editor, similarly to editing the content is not really possible in TYPO3 AFAIK - at least not out of the box. For this, you would need a template builder. The only thing I have seen so far that comes close to this is toujou (I am not affiliated with them, just wanted to mention it). They have something which you could call a website builder. But AFAIK, you can't download it, they provide this as a service.
The sitepackage builder - as far as I know - pretty much just creates a sitepackage based on the bootstrap package extension which you would have to further modify by editing the files.
What you can also do is edit the TypoScript in the backend. Just go to the "Template" module in the left column. But, this made more sense in the past, because a lot more was done with TypoScript. Nowadays, you usually use a combination of Fluid and TypoScript and you can't edit the Fluid files in the backend.
While in the past, a lot more was done in the backend or could be done in the backend, everything is moving towards maintaining changes in files and extensions, where the template is maintained in a sitepackage. For some things both is still possible (backend and extension), e.g. backend layouts, TypoScript etc.
Moving the configuration + templates from the backend (and storing them in the database or as files) to a dedicated extension has several advantages:
Every configuration etc. is bundled into one extension, this makes it easier to install in another site, on a testsystem, exchange it etc.
the sitepackage can be put in a version control system (e.g. git) which has a bunch of other advantages such as easy rollback to a previous version, referencing issues etc.
The downside is that you need more technical expertise and there is a learning curve.
see also:
The Anatomy of Sitepackages
Sitepackage Tutorial
I understand that it might be pretty cool to assemble a template in the backend - just like you can do with the content. Maybe someone else knows how to do that with TYPO3.
You can also check out these resources which seem to go in the direction of what you are looking for:
TYPO3 extension mask (documentation)
T3terminal
in the official documentation you can find the structure of folders where the files for your layout are stored.
More details on fluid templating in this document
Now you want a possibility for editors to select between different page layouts. An often used way is to use the possibility to select different backend layouts and select a frontend layout accordingly.
This is shown in the video on this page or in the documents you can find if you uses the searches on that page.
I was asked to improve the list admin for the medialibrary of a django website (built with FeinCMS) where images are very important. There should be only images in the list admin, and they should be many, and dense. Furthermore it should still be possible to mark images for bulk operations. So, I'm seeking for roughly what the Wordpress Media Library offers (sorry, collegues).
I'm sure that this problem is quiet common. However, I cannot find a plugin offering all the functionality I need, including the template, the static files and a place for settings. Is there such a plugin?
https://github.com/20tab/twentytab-customadmin
Should be what you are looking for, you can set icons for every section, and lot of other customizations.
As you may have noticed, the wiki module has been dropped in v7 of OpenERP.
The question is: what alternatives are there it? Is there any community module available or in the works, providing wiki (or even markdown) documents?
For what it's worth, here's a little more info regarding what I said in comments.
In OpenERP 7.0, the wiki module has been renamed/revamped into the document_page module. You may find this mentioned in the last section (8.3 Renamed Modules) of the OpenERP 7.0 Release Notes. It now uses a simple WYSIWYG/HTML editor and stores the pages as HTML, instead of the previous wiki/markdown-based syntax. Therefore you may or may not see it as a true "wiki alternative". The goal is to make it easier and more flexible to use, effectively providing a minimalist CMS system inside OpenERP: you can use it to add static pages in your regular OpenERP menu (or your OpenERP portal), organize them in section/categories, etc., using freely editable HTML (you can edit the HTML source if needed), while preserving their
Note that several issues in the initial 7.0 release might temporarily make the document pages less user-friendly than they should: the WYSIWYG editor was not enabled in all cases in edit mode (fixed now) and the editor is sometimes too narrow (should be fixed soon).
On a related topic, it may also be interesting to know that OpenERP 7.0 provides a collaborative writing solution via the new pad module, allowing you to embed etherpad-lite pads in your documents. It's integrated with the project and the note modules, and you can use it easily for your own custom modules as well.
The OpenERP Knowledge Addons features a module to support MediaWiki syntax (currently only available/verified for v6.1).
So, I've got an app that needs to deal with files created by Adobe InDesign (.INDD), and while the XMP Metadata is useful, there are additional things that I want to know about the files that do not appear to be in the metadata.
Specifically, I would want to know the number of actual pages (not just number of page previews created), and what the dimensions of those pages are.
Has anyone run across any toolkit, sdk, etc. that can get me this information?
This will be for a non-open source commercial app, so licenses are a potential roadblock. Also, this app will not be a plug-in for any Adobe product, so the InDesign Plugin SDK is not an option either.
C++ is the preferred language.
.indd is a proprietary format owned by Adobe. You are not allowed to interact with this format outside of InDesign. If the documents are saved in the .idml format, it's quite possible and not very difficult, but if all you have to work with is a bunch of .indd files that someone else created, you're gonna have to use a plugin or scripts together with InDesign.
We're in the middle of deploying a new software system to lot's of users in lot's of places (200+ users over 8 countries). In the past we've written a manual for the users, then update it every so often. This works ok, in that all the users ahve the same manual and it covers the main things but it has it's problems, like it doesn't get updated that often, we sometimes miss updates, and some users will have old copies.
We've been talking about using a wiki during the testing and deployment phases to build a knowledge base about the system. Ideally we'd then like some way to convert that into some form fo electronic document that we can then 'pretty-fie' and send out as the official manual, as well as letting users use and update the wiki.
Has anyone else done anything similar ? Any suggestions for wiki systems, workflows, document formats etc?
Most wikis support export via PDF e.g.:
MediaWiki PDF Export
DokuWiki PDF Export
TWiki PDF Export
You can write something that generates LaTeX from the wiki and renders a manual to PDF. With packages like hyperref you can retain cross-references as hyperlinks.
Additionally, you can integrate content from multiple sources such as a data dictionary into the LaTeX document, which can be mixed and matched with the wiki content. You could also set the architecture up so it can support cross-referencing that goes either way.
Framemaker could also support this using generated MIF files, and you could also use Lout in a similar way or convert your wiki content to docbook, which would allow you to use any of the many rendering options available to that format.
As an aside, the following Stackoverflow postings discuss various systems for maintaining documentation.
Application (Not a Markup Language) for Producing a User Manual
Can LaTeX be used for producing any documentation that accompanies software?
What tools are used to write documentation?
What tools does your team use for writing user manuals?
How best to write documentation (ideally in latex) targeting both the web (html) and paper (pdf)?
Best tool(s) for working with DocBook XML documents?
What is the recommended toolchain for formatting XML DocBook?
Is a successor for TeX/LaTeX in sight?
Madcap Flare is a help-and-manual authoring tool that uses HTML for the source of each topic. You could pretty easily do a mass import of the Wiki pages. Would then require some cleaning but after that you have a nice single-source system that can output CHM, web-browsable help, PDF, DOC/DOCX, etc.
How are you storing the help source at the moment? Is it MS Word files, MS help, LaTeX?
If you put your help source files under version control then you will get all the benefits of a wiki without having to migrate to a new system - people can make edits to the help files easily - those changes can be tracked, reverted etc. and you get the prettified manuals as before.
I followed Node's links and came across some mediawiki pages that I thought were noteworthy.
Extension:OpenDocument Export
Extension:PDF Writer
Category:Data extraction extensions
I gave a previous answer which may be useful for the "wiki to PDF" part -- look at using the open source PediaPress code or functionality. You can get ODFs from it too, although their PDFs are already quite pretty (but you might want to rebrand it and restyle it for your company I suppose).