We are using Plone 4.1.3, and have problem copy/cut and paste News Item from a folder to a collection (of News Item). We are getting this error when trying to paste the News items to the collection: Disallowed to paste item(s). We checked all the permissions and they are okay. Can somebody advise?
Thank you very much in anticipation.
cmgui
Collections are designed to be queries, not containers for content.
Related
I am following the Magnolia CMS documentation -
Creating Page Template. https://documentation.magnolia-cms.com/display/DOCS/Creating+a+page+template
How can I see the properties listed on one-pager-module/dialogs/pages/main.yaml ?
Thanks
How can I see the properties listed on one-pager-module/dialogs/pages/main.yaml ?
Those are dialog fields. For list of possible types of dialog fields see https://documentation.magnolia-cms.com/display/DOCS/List+of+fields
If what you want to see are actual properties with values in a page created by that dialog, log into AdminCentral, go to Tools menu and open JCR Browser in there, select "website" workspace and in the displayed tree of pages expand one you have created. It will list all the properties with their values.
HTH,
Jan
I assume you are looking for all possible options of main.yaml, therefore since its a template definition, one can find the relevant information from: https://documentation.magnolia-cms.com/display/DOCS/Template+definition
Cheers,
In Sitefinity, almost everything is able to be revisioned. In the backend interface at a page for a content item you can click on Revision History and see revisions.
We're in a situation where we're manually uploading documents in to the Documents & Files library through a custom form. We're able to do this using the Content Lifecycle which has pretty good documentation: http://www.sitefinity.com/documentation/gettingstarted/developers-guide/sitefinity-essentials/modules/content-lifecycle .
What doesn't have any documentation is how to modify a document so that it updates the revision of that document programmatically, not replace it. Right now, we're only able to replace it and the revision history stays empty.
I think you cannot keep the previous version of the document in Sitefinity.
The revision history for the documents keeps track for the metadata only, e.g. Title, Author, etc.
If you replace the file, there is no way to revert it back through the Revision History.
Disclaimer: I haven't tested this in the 7+ versions.
How can I get a Views block to query information from the page it's assigned to and filter it's output?
Please see graphic below to see what I'm trying to accomplish. (Open in new tab to enlarge)
views relationship http://reubenlara.com/blog/views-relationship.jpg
I found a similar use case here and it solved it.
https://drupal.stackexchange.com/questions/12388/making-a-view-with-a-node-reference-argument
R
I created a "View"* in Drupal to grab all the content and essentially make a site map, but I realized that it doesn't have an option to grab content from the Blocks I have created. Does anyone have an idea if I can even do that?
If not, should I essentially make each block a page so that it can crawl through the pages? I worry that this will end up becoming unmanageable in the end... What are some other options/work arounds? My end goal is to make a site map - maybe I am making this too complicated?
*To make my view I did:
Administration->Structure->Views->Add. Then I made it a page, called it "site-index", and made it "show Content of type All" (with tagged field empty). Then I chose "Content: Title" for my Fields and my Filter Criteria is set as: "Content: Published (Yes):" - That way, it will grab the titles of my web pages.
Thanks, and please reply if further clarification is needed!
Apologies if I'm wrong but I think there might be a bit of confusion over terminology here. In the context of a view Content means nodes, not all HTML content on the site. Your view will return a list of all published nodes, which are essentially the pages on your site.
On a normal sitemap (if there is such a thing) you would only link to full pages, not to parts of pages like a block, they are essentially used to provide a hierarchical overview of your site to aid navigation for users and, probably more importantly these days, search engines (you can submit an XML sitemap to the major search engines instead of this but that's really for another question).
Rather than doing this yourself I'd actually recommend you download and install the Sitemap module which will do all of the work for you, as well as arranging the content in their respective hierarchy.
I have a fairly new drupal installation with a few hundred nodes. I moved it from the development server to the production server.
However, when I opened my homepage, it says page not found. After checking all my links, it seems that I can't get to any of my content. They exist in the node database, as well as the content type tables. I verified that all my URL aliases are also in place. In most cases, I can still see all the information from views I had created, but when clicking to see the full node view, I get the "Page not found".
I did trim all my cache tables before importing to reduce the size of the DB. Has anyone had these symptoms before? Perhaps there is a particular table, that when truncated, will lead to this problem?
**Update: Imported my revision table again, and presto - Although my content came back, I'm still having a sort of permissions problem. When an anonymous visitor comes to the site, they are told they don't have permission to see items like content type "Page", yet in user permissions, everything looks good (definitely good before migration) perhaps another deleted table?
Yes, node content information is in the revisions table, not the node table. You REALLY need the revisions table. I assume you can just remigrate again, this time without truncating revisions.
if table is broken, it shouldn't show "Page not found". It may show that sql error that table or column doesn't exists.
Try troubleshoot in http://drupal.org/node/201875 (you will see Page Not Found links in middle).
Also may be you use some redirecting in your node theming, check this.
p.s. In any case, node saving touch 2 tables: node and node_revisions