In our installation, I can only see Building Block from when connecting to CME using WEBDAV. I am wondering whether it is possible to show structure group as well?
Unfortunately not. Only the Building Blocks folder is exposed to WebDAV. This behavior is not configurable.
Related
As answered in multiple options for a community connector configuration in Google Data Studio, it seem no possible this.
As far as we can see now, for connectors like Adwords, DCM and Google Sheets the configuration is dynamic (updating configuration values based on something already selected in the configuration).
Anybody have any clue on how this is being done?
Thanks in advance
Update (2020/05/05): This can now be achieved through Stepped configuration in Community Connectors.
Original: Adwords, DCM, and Google Sheets are native connectors in Data Studio. Community Connectors are implemented differently using Apps Scripts and thus have limited functionality compared to some native connectors.
That said, if you would benefit from this feature, please submit a feature request / vote for it.
Currently I have a task of exploring Alfresco Community 4.2.
What I need to do is to build a workflow that allows users to upload document, an admin to verify it, and other higher level users to allow the document to be released, how it is released is not my concern. e-mail notifications will also be sent to higher level users or admin when the document is about to expire.
I have downloaded the Alfresco Community 4.2 exe from their website, and install it in a Windows 7 32-bit laptop. But I cannot access to /alfresco and /share, I learnt that I need MySQL for this, so I'm currently installing this one, http://dev.mysql.com/downloads/windows/installer/ , am I correct?
And do I have to do all this separately, for example, first I need to set up users, then configure their restrictions, then move on to documents?
I'm really really new in this. I've searched Google but so far everything seems complicated to me.
Thanks in advance!
First of all if you are using installer which you seems to be you do not need to install anything separately. Alfresco installer comes with everything bundled into it's installation.
Unless you have specific requirement where you want to use MySQL instead of bundled postgres database.
Now For workflow one everything is up and running you can check various existing out of box workflows available with alfresco if any of that meet your requirement you can use that directly no other efforts required.
In case you feel none of those workflow meetup your requirement then you need to create your advance workflow.
http://wiki.alfresco.com/wiki/Workflow
This link contains all you need to know regarding alfresco workflows.
I am trying to understand different artifacts around implementing Tridion XPM. Unfortunately I did not find any article that has answers to my questions.
For example Content delivery server (on WebSphere) can have four different applications, one for Content delivery(which handles publishing), one for web service (oData implementation), one for XPM (with Session preview) and the actual preview application. I am assuming we can merge one or more of these applications into one for a simple implementation (with one or two consuming websites).
My questions are:
How can we simplify the number of applications (WARs) to be made? Though I always prefer to keep the preview application separate from Tridion's framework. What are the benefits around Content Delivery session preview Web service as a standalone Java/JSP Web application Versus adding it to existing application?
How can I associate/integrate webservice(oData) to XPM or other common basic functionality like component linking?
For example if I publish a page with out enabling oData it will split tridion:ComponentLink tag where as if I enable it will split tcdl:Link tag. So I need to come up with custom class to read these tags? which eventually require adding Tridion framework in the preview application. (Assuming I did not include any Tridion framework in my preview to have a clean application dependency)
I looked at Tridion's live site for more information, but I could not find much useful info for my questions.
There's a LOT of questions right there, let's see what I can do here.
You will need 3 applications:
A Deployer (standard deployment configuration)
A Staging Website (with Tridion stack + XPM Filters + Ambient Framework)
A WebService app (OData + Ambient Framework)
XPM itself runs in the Content Manager Explorer, so it's not per se a separate app, it's an extension of the Tridion Content Manager.
If you want to have your staging separate from Tridion, then you will not be able to use "Session Preview", which in turn means you do not need OData. This however will revert back to the SiteEdit days whereby every change you do to pages requires the page to be republished (with Session Preview this is immediate).
You do NOT need to use OData for your Website in any way (unless you really want to). The WebService is there to support Session Preview only. I wrote down the interactions between XPM/CME/Staging site here and they're documented here.
If you publish tcdl:link code to OData, then just use TCDL/REL, Tridion will render it for you, you don't need to custom parse anything.
Hope this helps...
We are using Tridion 2011 SP1 and DD4T framework.
We have websites in both Staging and Live servers. We have published to both the servers from Tridion 2011 SP1 using different targets (Staging and Live). Now i am planning to add staging servers into Live target, So while publishing to Live it will be published to staging also. I am not going to use Staging target after this.
Here my question is. Will it create any problem or any issues in this. Does it have any disadvantage?
Thanks,
Jagadeesh.
So, all you want to do is to publish to Staging also when you publish to Live?
If this is all you want to do, then the easiest is to chain both Publication Targets with the same Target Type. Open the Staging Publication Target and in the advanced tab, link it with the Live Target type (and unlink it from the Staging Target Type).
You should probably also remove the Staging Target Type so as to not confuse your editors.
PS - I am answering here, but your question is not a Stack Overflow/Programming question. You should have asked this in serverfault instead.
2nd part of the question: Will it cause issues?
Think why you had staging to begin with, since you're going to lose that now. You are probably removing the ability to implement Experience Manager (ex-SiteEdit), but maybe that's not a requirement. Staging is also typically a smaller environment. If you're doing this because you need more capacity on your Live server, then you should have considered buying a new server instead, and linking it to the same database (since you're using DD4T there's no nastyness related to file system replication or multiple deployers).
What is meaning of ACTIVE in ASP.NET(ACTIVE Server Pages)?
Can you please provide an explanation on why it is named 'ACTIVE'?
Active was one of Microsoft's favorite words when the original ASP first came out. Other items like ActiveDirectory, ActiveSync, and ActiveX Data Objects also came out of this mid-late 90's "Active" era.
It had more to do with marketing than anything IMO.
EDIT: And ActiveX and Active Accessibility...
This is referring to the fact that the pages are running ActiveX scripts and server controls, from here:
Microsoft® Active Server Pages (ASP)
is the server-side execution
environment in Microsoft Internet
Information Server (IIS) 3.0 that
enables you to run ActiveX™ scripts
and ActiveX server components on the
server. By combining scripts and
components, developers can create
dynamic content and powerful Web-based
applications easily.
It is due to you are Actively Running Scripts.
Developing functionality in ASP websites is enabled by the active scripting engine's support of the Component Object Model (COM), with each object providing a related group of frequently-used functions and data attributes.
See here.
This is purely my opinion (and not necessarily the fact) but I would assume because unlike an HTML page it's not static. It's just another word for Dynamic.
Edit: David's post offers a better actual description of it.
i think it might have to do with ActiveX ... see here -> http://en.wikipedia.org/wiki/Active_Scripting
An active web document consists of a computer program(JS,applet etc.) that the server sends to the browser and that the browser must run locally. • When it runs, the active document program can interact with the user and change the display continuously.
It means that the pages have behavior... that they act to generate the result the user sees, rather than simply being a copy of the document the user ends up seeing.