I cloned some magnolia content app examples and can't understand, how to generate magnolia bootstrap xml files. They are too big and to write them manually is too hard.
I think there is a way to generate them automatically.
Magnolia Bootstrap Files are created within Magnolia. Just create the content you want to bootstrap and export it. Some Apps like the pages app or the config app have an "export" action in the action bar. It is also possible to use the export app to create bootstrap files for all kinds of magnolia workspaces.
As Thomas said, you should not hand write bootstrap files, but instead export configuration or data you want to bootstrap from Magnolia.
Since "what you want" seems to be creation of apps, you might want to look at a script to create them (so you can them export such created app as a bootstrap file) mentioned here.
HTH,
Jan
Related
I'm developing a new Hugo site and in this case I thought to create also a template so.I can use for future site.
Well in the template there are tons of vendor files and library because depending of the pages that the site will implement these library will be used. The problem is on the deploy. For example I use Line icons library that has a lot of .png files. (For example 200 files).
Well in the template I put all the files but could happen that in the site that implement this template I use only five icons. Is there a way that look around the final HTML and the usage of the icons and delete in the public folder the not necessary files?
Not directly.
You would need to add an utility script to your template, in order for any user implementing said template to be able to call this script on demand.
That script should then be able to:
analyze the HTML files generated in public_html
cleanup the icons accordingly
I'm trying to find a solution for files uploading directly with TinyMCE. Imagine creating a list of pdf files by uploading them using a custom button.
Is there something already done I can use? collective.clipboardupload seems to be a solution only for images.
collective.quickupload serves us well for such purposes and has a very good UI.
You can add that gadget as a portlet and make it only visible in edit-mode via CSS.
In our case we assigned the portlet to a certain content-type ('Gallery') instead to a location.
MoxieManager may be what you're looking for. It's a premium plugin made by the same developers as TinyMCE itself.
https://www.tinymce.com/docs/enterprise/manage-files-and-images/
Try to use reponsive file manager :
http://www.responsivefilemanager.com/
I'm experimenting an issue when I export customizations made by Studio tool, any custom fields are not exporting. I mean, when I load the package created in developer server to the production server, there are not custom fields in EditView, there are "native" fields only.
I'm using SugarCRM 6.1.6 (I know, it is an old version, but I can't update it right now)
Regards
Mauricio M.
You may just need to do a repair and rebuild - that's the likely quick fix. Alternatively, ensure that the package on the dev server exported both the custom fields and the custom layout metadata (i.e. the edit and detail view layouts). If it did, double check the permissions in custom/modules//metadata to ensure that the files were able to be uploaded and are readable by the web server.
I have installed TYPO3 on my web server and it use the "Introduction Package" template.
The problem is that I have to work on another TYPO3 online website that use a custom template.
Can I obtain the template of the online website and use it on my local website? (to perform some test in local).
I saw that TYPO3 uses various templating systems and I do not know how this could affect the export\import operation. In Joomla or WP I simply take the template directory and then I copy it into the themes directory but I think that in TYPO3 this operation could be more complex.
The fastest way is to copy these directories:
fileadmin
uploads
typo3conf/ext
and the complete database, then you have "cloned" the original website locally. (assuming that the core stuff is loaded the default way, with symlinks)
Then you just need to edit the database connection stuff and maybe some paths for image magick and so on in the typo3conf/LocalConfiguration.php.
I have a web app project that I will be starting to work on shortly. One of the features included is going to be a content management system where users can add content and then that content will be combined with a template and then output as a regular .html file. This .html file would then be FTPed to their own web host.
As I've always believed in not reinventing the wheel I figured I'd see if there are any quality customizable CMSes out there that do this already do this. For instance, Blogger.com allows you to post all of your content to your account there; but offers the option to let you use your own hosting. Any time you publish a new article then a new .html page is generated (as well as an updated index page with links to the new article) and then the updated content is FTPed to your own server.
What I would like is something like this that I can modify to more closely suit my needs.
Required Features:
Able to host on my own server
Written in PHP
Users add content through their account, then when posted it is FTPed as .html to their server
Any appropriate pages are also updated to link to the new content (like the index page or whatnot)
Templateable
Customizable
Optional (but very much desired) features:
Written in CodeIgniter or a similar PHP framework
While CodeIgniter isn't strictly required, I would very much prefer it. It speeds up development time and makes things much easier to implement.
So - any suggestions? I've stumbled across a few CMSes that push to remote servers as static pages, but the ones I've found all are hosted on the developers servers which means that I cannot modify it at all.
Adobe Contribute might work for your situation. A developer/designer creates a set of templates with Dreamweaver and publishes the templates. Authorized users can then create pages based on the templates and only make changes within the editable regions. It includes systems for drafts and reviews prior to publishing (via many options, including ftp) and incorporates automatic version control. It can work with static html pages or dynamic pages like php.
Sounds like you need a separate application that can do this for you.
For example, you should be able to write something that queries Drupal's menu router and saves the output (with curl) to a directory and then run's rsync to push your content where you want it to go.
Otherwise your requirements are likely to be outside the scope of a typical CMS. Separating this functionality will give you better options.
You'd need to write a filter for your URLs too. It's a bit of work...
Hope that helps!