Where to find the tags used in theme short codes? As well as the general tags used in pyroCMS? - themes

I was wondering where to find the tags to type to take advantage of shortcodes programmed in themes. Many themes have them, such as the one below. However I can never find the information required to make use of them in the read me's or on site documentation. Which makes using them impossible for me. Is there a specific html, css, or php file that is consistent to each theme and shows them?
Given the lack of write ups on what tags to use suggests that theme creators expect people to know which file to find them in.
https://www.pyrocms.com/uploads/default/store/listings/11-25-2012_9-41-20_PM.png
https://www.pyrocms.com/uploads/default/store/listings/11-25-2012_9-41-20_PM.png
On a more PyroCMS rather than theme specific note, is there a list of all tags and their uses? Such as {{ settings:site_name }}, or the page body tag. Every link I have found to a list says that the list has been moved.
Thank you for your time once again.

Open up your file directory and navigate to:
path/to/your/files/system/cms/plugins/theme.php
Each one you can use is listed here along with an example in the function description. Each plugin in this folder is lined out the same way (files, session, asset, etc). You should be able to view each one and play with how to incorporate them into your project.
Edit: Also, you can find more information here: http://docs.pyrocms.com/2.1/manual/plugins
Notice that this is specific to version 2.1. If you are not using 2.1, in the top navigation add click on documentation and then select your version.

Related

Joomla - Modifying default category list view (through overrides?)

I'm building a site for a friend and I should state that this is not what I'm doing for living. I just started working with Joomla a few days ago.
Everything is good so far, except I'm stuck at one point.
This is a site for a construction company and I need to create articles for on-going and completed projects. I will create an article for each project and each article will belong to a category, 'Completed' and 'On-Going', respectfully.
I plan to create menu links for 'Completed' and 'On-Going' categories in main menu. I also want to present a thumbnail of the article on the category list. Problem is, standard look of the category list is kinda ugly, and I have no idea how to change it. I'm using a template named PixelDot, but it does not seem to do any good for my problem.
During my research, I stumbled upon concepts 'Layout Overrides' and 'Alternative Layouts'. I have basic html and css knowledge, also some PHP, but I am totally lost on which file(s) to modify. I also need a little help on get the entry text picture as a thumbnail on the category list (this is the list where you see 'articles' aka projects which belongs to the category (completed or on-going), when you clicked on relevant menu button)
Any help will be highly appreciated. My Joomla version is 3.4.1. (which I believe most up-to-date version as today)
I'm sometimes making it more complex while I try to make things detailed and clear, I hope this is not one of those cases.
First, I would suggest using tags rather than categories to manage this. Tags are much better suited for temporary labelling or dividing into groups.
Second, go to the template manager, template view for your template.
Go to the create over ride tab and select the view that you want to override (i.e. tagged items).
This will automatically copy all the files to the correct location in your template.
At that point you can play around with the layouts to your heart's content.
Also ... some pieces of the layout you may want to override may not be in the traditional layout but may be in a jlayout. You can do the same thing with them. THis is all documented in the docs.joomla.org site as well as around the web.
I also would do this with Tags. One reason is, assuming you are using SEF URLS, that the projects article pages will have a unique URL. If you move a project's article from "on-going" to "completed" then you may be changing that SEF url. This will cause your search engine ranking for that page to be lost.
I would tag each article "on-going", "completed", etc and then create a menu item to display only that specific tag. The project's article would stay in its original category, that could be my project type, project location, etc; which also will increase the SEO for that given project's article.

Possible to include an image in the meta data in code? VS 2013

I would like to be able to include a screenshot of a control inside my code, this way making control identification easier for new members on my team, is such a thing possible?
Maybe even the ability to just have the image on a network share with the path in a comment, and then have a plugin that when hovering over the link brings up the image?
EDIT (More detail):
I'm creating a test project, the application under test has over 1000 controls, some of them are similar in name and purpose, this can make it difficult at times for developers to reuse the API I am creating because the control name is simply not enough for quick identification of the control in use.
I use the word API very loosely too, none of this stuff will be consumed in web services, and it will always be white box with developers including a project reference and have direct access to the source code.
For every form in my application (The test one), I have a controls.cs file where all the controls for that form in the application under test are listed - This is where I want the hover to screenshot ability in the control definitions.
Another sure factor is that all developers will be using VS2013 (For now the base version), later this could be update 1 or 2.
As the initial author and senior developer on this project, these hover / image references (in the code) will be as useful to me personally as any 3rd party developers, or any later developers to join the initiative.
Thanks again, and I added a bounty!
I believe you can use Whole Tomato's free SourceLinks Visual Studio extension to do what you want - or at least get pretty close to it.
Built-in Functionality:
Out of the box, the extension allows you to specify comment patterns you want users to be able to take an action on. Once the patterns are specified, SourceLinks will highlight any occurrences of those patterns in the text editor. You will be able to double click the highlighted items and perform a pre-configured action (such as opening a link in an internal/external browser, or launching an executable).
You can see an example in the SourceLinks configuration dialog shown below:
(source: wholetomato.com)
So you could use this feature pretty painlessly to define a keyword such as Control Image and then put comments like the following in your code:
// Control Image: my_smart_list.jpg
SourceLinks would allow you double click this text, and you could have that configured to launch the image (using a file:// or http:// url depending on how and where your images are stored) either inside Visual Studio in it's internal browser, or in an external browser.
Custom Tooltips!
Now, if you want to put in some more effort into this and actually write some code, then SourceLinks allows you to create API Extensions to display custom tooltips when the user hovers over the marked text in the editor. The default installation of SourceLinks comes with sample API extensions that you can copy to create your own. See the article linked at the very top of the answer for more details on these samples.
This post in the SourceLinks forum informs us that SourceLinks expects the custom API Extension to return the tooltip value as FlowDocument XAML text. This is awesome news for us, because a FlowDocument can contain many types of elements, including formatted text, hyperlinks, and images.
Imanges in a Flow document can be specified both inline as well as externally.
Hope this helps!
I would use doxygen -- create the images somewhere in the source tree and use doxygen comments. You can embed the \image command in source comments (see docs) and doxygen will generate all the HTML documentation from there. I think doxygen is a great tool for documenting a codebase as you can generate the documentation directly from comments in the source and distribute or host the HTML separately.

Mediawiki - a quick link to template editor

Wikipedia's navbox templates have v·t·e (view, talk, edit) links in upper left corner.
Now I have my own MediaWiki installation and want to be able to edit templates quickly (to have an edit link near each template or more advanced - near each template of certain type).
How to do this?
P.S. I am not sure whether this is the right place to ask such questions, but saw mediawiki tag on stackoverflow.
The links in navboxes are there, because a navbox template is created using Template:Navbox, which in turn uses Template:Navbar, which actually creates the links.
If you want something similar on your wiki, you can copy Navbar from Wikipedia, create your own version of Navbox (or whatever) and then use that in the specific templates that you create.

Why won't Joomla render my PHP/Javascript tags on the front page?

This is my first project on website development using Joomla. I am trying to make a dashboard implementation. My problem is that whenever I edit my script in article using source tags, the changes are not reflected on my site immediately. I have even tried restarting my Wamp server, but in vain. Any tips that I should follow?
Thanks.
Depending on your Joomla-Version there are different options to check to suppress stripping or filtering of tags like <script> for the frontend. Here are some hints:
First of all your tags could be filtered out client-sided depending on the editor you selected. If you use the standard TinyMCE e.g. go to Extensions - Plugins - TinyMCE where you will find a list of prohibited Elements which may include script. Be exactly sure what you do though, always check who should be allowed to enter script tags in an article, this is almost always a major security risk if anybody else like you as an administrator has the right to use them. So another option could be to just set the editor for your administrator/author accout to plain text and leave TinyMCE untouched.
Another filtering is done server-sided by joomla itself which can be controlled in "Global Configuration" -> "Text filter". After a standard installation all groups will use Default Black List filtering which includes removing script tags. Here you could define "No Filtering" for the Super User group e.g.
Again, all this depends on your Joomla-Version (my examples are referring to 2.5) and are hints to get around the issue but without knowing your security concept.

Custom landing page with Octopress

I've setup Octopress and want to use totally custom styling basically throwing out most of the standard styling that applies to the rest of the site.
I do want to keep reference to all responsive goodness though that is baked in.
What's the best way to setup my custom landing page?
You mean like this?
http://eduncan911.com
^- My Octopress site.
Blog is at: http://eduncan911.com/blog
Since Octopress uses Jekyll under the skin, it would be better to think about how to accomplish this in terms of Jekyll - and there are many ways to do this.
OT: Personally, I find Octopress' theme layout, includes and customs far too complex and too granular. They did this to make it highly customable; but in my view, it tightly couples every template to another template.
Now with that said, there are multiple ways to achieve this. I did answer a very similar question here:
Creating an octopress theme from a wordpress theme
It's Jekyll: therefore, just go create the page however you want it. Replace the /source/index.html with whatever design, html and css you want.
If you don't want the blog roll, or want to move the "blog to another directory", just move the current /source/index.html to, say, /source/blog/index.html. That's it.
As I noted in the answer above, the only import thing is to keep the YAML frontmatter and specify the "layout" as you want to use. For example, I have a layout called "homepage" that is far different than any other layout. My /source/index.html uses layout: homepage.
But even then, you don't even have to use the YAML - create your own raw html file as you see fit. It will be used when you rake generate. This is what I personally did at first. Then, I slowly split up the homepage into the /source/_layouts/homepage.html and just went from there. I did not follow Octopress' entire theme at all - just enough to use posts and pages.

Resources