I am aiming to make an alfresco site Taggable.
When creating a site, I am looking for a simple way (JS, XML) to let users assign Tags to a site.
It can be done by assigning Tags from Repository to the site folder, but what I want is to add Tag field to the site creation form.
Change the create-site.get.html.ftl use the alfresco\components\form\controls\category.ftl as reference to create the tags field.
Then change the sites.post.json.js in org\alfresco\repository\site and get the tags and add them to the site.
You'll probably also will need to change the client-site JavaScript create-site.js to send the actual tags value to the repository webscript.
Related
I have a custom domain setup with Firebase Dynamic Links. The URL prefix is https://example.com/link and I am then able to create a new dynamic link that will resolve https://example.com/link/article to https://example.com/article within my app or on the website.
What I need to do is also pass the ID of the article that I want people to see. The copy writers need a URL structure that lets them cross-link articles, so it needs to be a URL like this: https://example.com/link/article?id=123456 but when I test this in the browser it resolves to https://example.com/article .. this should be possible right? I shouldn't have to create a dynamic link for every single piece of content should I? Would I need to add https://example.com/link/article/123456 so it links to that specific article?
If I were to create Dynamic Links using the REST API in a Cloud Function that is triggered when new content is added to the Firestore, would these links persist?
I know that using the long Dynamic Link format will give me what I need, as I can create the short URL with the param added. But this doesn't solve the issue of giving the Copy Writers a URL structure that is easy to use in their content. Maybe a Cloud Function that strips out the URL links from the body copy, and replaces it with the long-form Dynamic Link?
Is this possible to achieve without too much effort or a plugin? It's simply to instantly redirect to a site I've made in my portfolio if the post doesn't have any content.
Note that I don't want a script in the actual post to redirect since I only use Wordpress as the backend and fetch all the data to be used by a JavaScript backbone app.
EDIT : Added some extra info in a comment
Short Answer: No. You cannot set your Post Permalink to an external asset without directly editing the database.
Long Answer: First off, you need to understand the purpose of the Permalink. It isn't just an arbitrary link to somewhere. It's reserved specifically for storing where that specific post lives within the context of your Wordpress installation.
Your post doesn't live on example.com. It has its own ID, and Wordpress has a specific spot set aside for it where it can be seen on YOUR domain. Leave it as such.
Instead, what you should be doing is employing the tools Wordpress gives you to achieve what you want. A Plugin doesn't exist for what you want because - quite frankly - it's a fairly trivial task when approached CORRECTLY and doesn't warrant the use of an external resource.
So what's the correct way?
Use a Custom Field. Name your Custom Field something like 'externalHref' and fill that in with your link to the website you want to point to in case there's no post content.
Then in whatever templates you're using to generate your posts, just check either for the existence of your Custom Field called 'externalHref' or check for the non-existence of Post Content. In either case, instead of generating a link using The Permalink you can simply build a link that points to wherever you need.
I just first want to say, thanks for taking the time to read this!
I have an e-commerce website running the content management system DotNetNuke, which I believe is built on the asp.net platform in a windows server environment. The specific module that powers my e-commerce store dynamically generates pages for each of the store categories, as a user browses through the products available. As you may be aware, modules such as these must be placed on a specific page, and all the dynamic content generated by the module must reside on that "parent page".
The problem is that while the module does allow me to add HTML text for H1's and H2's on these dynamic pages, it does not support adding page meta tags such as "title" and "description". As a result, all of the dynamic pages generated by the module pull their meta tags from the parent page, making it difficult for Google to understand what I'm trying to show the user. This also causes google to show all these generated pages as having "duplicate title tags" in my analytics.
The temporary fix:
I have removed the title tags from all of these "parent pages", in hopes that google will decide to generate it's snippits from the H1 and H2 tags residing on the dynamic pages. Was this wise?
Now for the question:
Is there any kind of solution available which would allow me to manually assign meta tags to a page I specify in my hosting environment? As I stated earlier, I am able to add body HTML code to pages. Is there any way to force a page title tag from code placed in the body? Is there a better way to do this? You can view my problem in action at www.yandasmusic.com
Thanks for your time and patience!
Alex
The temporary fix: I have removed the title tags from all of these "parent pages", in hopes that google will decide to generate it's snippits from the H1 and H2 tags residing on the dynamic pages. Was this wise?
Blockquote
No, not particularly wise. The page title is important.
The first route you should take is speaking to the module developer. They should know about replacing page meta information on a per-product basis.
You can get (limited) results by varying the page title/description using javascript when the page loads. Just keep the js simple and use the DOM information already on the page (ie, read the product name).
I posted a blog about this recently : http://www.ifinity.com.au/2012/10/04/Changing_a_Page_Title_with_Javascript_to_update_a_Google_SERP_Entry
The javascript fix will probably work if you set it up correct. But you really need to convince the module developer to change the way the module works, as bdukes has posted.
Don't bother with the Meta Tags - none of the search engines really read/use them because they are so easily spoofed. Just concentrate on the title and description of the page.
Ideally, your store module should be setting the page title and other meta information. In DotNetNuke, you can access the Title, MetaDescription, and MetaKeywords of the page by casting Page the DotNetNuke.Framework.CDefault type. If the store module doesn't provide this, you should ask the developer to add the functionality.
First of all, I am absolutely new to WP.
I am hoping to build a site using WP and figured out how to manage every thing except one feature. The feature that is required is to be able to submit a form with files (images in particular) by a non member.
For example, you should be able to visit the site and fill a form and submit your image along it.
Is it possible to upload files as above? How is this achievable?
Thanks in advance.
If you are not a wordpress coder , I would sugest you use a plugin for that .
Some options :
http://wordpress.org/extend/plugins/user-submitted-posts/
http://wordpress.org/extend/plugins/tdo-mini-forms/
http://wordpress.org/extend/plugins/quick-post-widget/
http://www.gravityforms.com/category/features/
and many more ..
read also this tutorial : http://wp.tutsplus.com/tutorials/allow-users-to-submit-images-your-site/ - it is not for VISITORS but for registered users - but it might help you to understand what is needed to be done .
I would use the Contact Form 7 plugin to do this, as it's extremely easy.
In the plugin settings you'll be able to choose what parts of the form you'd like to include, adding a way to upload is one of those options. You can even limit the type of file that is being used as well the max file size.
Once you create a form in the settings, you just use its shortcode to add it to your Wordpress page.
Yes you can upload file, but it is not a Wordpress specific solution, unless you want to use a plugin. You can code html/php as per usual to achieve it:
http://www.w3schools.com/php/php_file_upload.asp
To embed it on a page, you can create a Page in Wordpress, and assign it a custom page template that you create with the upload form:
http://codex.wordpress.org/Pages#Creating_Your_Own_Page_Templates
so..I created page--front.tpl.php in my theme directory and it works fine.
now, how do I make a variable that can be used in the page--front.tpl.php?
I can write my php codes inside page--front.tpl.php, but I think there is a better way.
added:
on the front page, I am going to query video and news nodes ONLY. That is why I want to make a new module for only front page.
any suggestions?
I'm not sure what you are trying to achieve here, but OK. You have two options: one is what you're doing now. Write your custom PHP in page--front.tpl.php and you'll be fine. The other is ditching the file and working only with page.tpl.php.
The variable $is_front tells you whether you're on the front page. You can write custom PHP in a conditional block: if ($is_front) { ... }.
Also, you can create a custom block (a view, perhaps, depending on your needs) and set its display restrictions to "only on the listed pages" - and list there. You'll have a custom view loaded only on the front page.
All you need to do have a custom front page is configure your front page in the site information settins (admin/settings/site-information in D6).
Creating a module to display that content is then a completely different thing.
What I would really suggest is looking at Views if you don't know it already. That allows you to build lists of things (nodes, users, ...) and expose them as pages, blocks, rss feeds and much more. You can create a list of nodes with types video and news, expose that as a page and then just point your front page to the path of your view.
you might try using the views module to create your list of videos and nodes. You can set a views page to be your homepage in the site settings.