Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 10 years ago.
Improve this question
I want to insert google analytics tracking code in my joomla site.
so i registered in the official site of google and saw there is an advanced tab with three more options than standard.
Do i have to check "i want to track dynamic pages" and "i want to track php pages"?
Do these options provide me better results or they are necessary for a dynamic site based on php like joomla?
Also where do i place the tracking code? Because of some bugs some say it is better just after the tag whereas other say just before the tag.
Thank you
General SEO advice: with Joomla you don't need to track pages dynamically, if you want, you can turn on SEF and use robots.txt, ror.xml and sitemap.xml (the first and last files are very important to google).
I also recommend on using Google webmaster tool to update Google whenever you post a new article as well as to check if there are crawling errors and remove "bad" URLs from google.
Like I commented on the other answer, tracking code should be located just before the closing tag for your web page - I recommend on placing the tracking code in the template! (even though you can copy and paste it separately into each article - this option should be done only on rare cases that you need to pass different parameters to GA from different articles.
Update:
Regarding your comment: yes, if you go to the "admin" section, then to "tracking code" you'll see the following option:
All it does is provide a different way of including the tracking code in your pages. I got to admit that I didn't use this option with a few Joomla and WP websites I've dealt with, and it still works totally fine. But if Google recommend on doing so - by all means go ahead and do it!
Judging by this source on setting up GA, it is important for PHP websites that you include the google tracking script at the bottom of the page before the </BODY> tag. I'm struggling to find any information that would give relevance to the questions you have mentioned above, beyond the fact that choosing different checkboxes shows you different instructions to setting up your script.
Related
We plan to create a FAQ website. It will include two types of content:
Lists of questions (FAQs), and
HTML for each answer.
When user chooses a list and clicks a question, the answer will load in Ajax style.
A very similar approach was described here: Ajax FAQ loading using jquery?
But, before we start developing our own CMS, we would like to make sure that no existing solution is directly applicable. So, my question is: are you aware of any existing CMS for creating Ajax-style FAQs?
We are particularly interested in WordPress plugins (one is listed in my own answer below).
Two solutions I found that are likely to be applicable:
WP DS FAQ: FAQ management tool for WordPress. Replaces specific code on a page with a pre-defined list of questions and answers. Requires WordPress version 2.7 or higher, compatible up to 3.2.1. Last ipdated in August 2011.
Core Design FAQ plugin for Joomla. FAQ is created out of a K2 content module. Requires Joomla version 1.7. Last ipdated in August 2011.
helo all!
i want to see the numbers of comments of any article on frontpage in joomla.
how can I add this plugin or module for the readers know the numbers of commments per article...
sorry for my english :D
Which component are you using for commenting? There are a bunch out there - in terms of displaying comments on the front page, I think you would probably have to contact that developer to see if they have a plugin to help with that, or write some code of your own to assist with that (it shouldn't be too hard - some templates have that functionality out of the box even).
Ultimately it will depend on which component and if the developer has already created something to go along with that plugin.
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 7 years ago.
Improve this question
If you have trained a new Magento developer what were some if any dummy tasks you have given them. Besides reading all of the articles out there and doing the examples, I am looking for some ideas to give developers to work on after reading as much about Magento as they could without actually working on a task.
If anyone has any good ideas please let me know, You can even post some good code snippets of possible answers and what not. This might be a good thread to keep if we get a lot of good answers, for us tech leads out here responsible for training.
They could be frontend design template or building modules, it doesn't really matter. If someone posts a really good example, I will mark that one as the answer.
Not sure this is appropriate for Stackoverflow, but not sure where else to put it where it would be answered with quality responses.
The tasks I've given before really depend on what the developer needs to do as part of their normal job. I tend to give tasks that force the "rabbit hole" situations early on in the process, and make sure that the developer has enough support to come and ask when they get stuck.
For frontend developers, the best thing to do is develop an actual theme, or whatever tasks need to be accomplished in some current project. As examples, ask them to:
Create a new theme directory w/ skin directories, etc
Change a template (the product/list.phtml and product/view.phtml are both common here) to accomodate some desired new functionality.
Add a JS lib to the product page for zoom or some other functionality, to be loaded cleanly using Magento's facilities.
Create a new page, including complete controllers and layouts as appropriate, with functionality to be fleshed out by a backend developer.
Change the CSS to the One Page checkout to fit the new site theme, without breaking CSS for the rest of the site.
For backend developers, again the best thing is the real thing. Developing backend modules takes some significant familiarity, but hitting the highlights isn't too bad. Examples:
Start a new Magento module.
Override a core Magento class with one from the local module
Create some administrator functionality to deal with the new module.
Add an ACL so that this functionality can be enabled / disabled for particular admin users.
Integrate with frontend code (see the frontend developer above) to provide the functionality to the end user.
Append to the system configuration to use the new functionality as part of the normal system.
These are just general ideas, but they will quickly force a developer to gain some understanding of the way Magento is laid out and how it operates. Of course, it can take weeks or months of supportive mentoring to get the developer to the point where they are a self-sufficient developer on Magento, but that's largely a matter of filling out the details after items like this.
Hope that helps!
Thanks,
Joe
This is what we send applicants to see if they even know what magento does/how it works ... not sure if this is what you meant ...
Please perform the following:
Override a controller action:
Override the Mage_Customer_AccountController keeping all the original functionality except that the logoutAction redirects to the home page immediately not the logoutSuccess page.
Override a model function:
Override the Mage_Customer_Model_Customer model keeping all the original functionality except that the getName() function always returns "Magento Rocks".
Modify a Block:
Change one of the blocks used on the customer/account/index page to display a message of your choice.
Add an Observer:
Add an observer so that after the order has been created on the frontend the last name gets changed to "Is Awesome"
Its not really practical ... at all ... but it lets us see if people can code in Magento in a decent way instead of just modifying core files and such. As with almost anything in Magento there are different ways to accomplish the various tasks, perhaps have them figure out the different ways or have them determine which way would be most appropriate.
Note: Just to emphasize so that no one points it out, these "tasks" were not designed for practical use and in fact you probably will NEVER do any of these, they were intended to see if someone could actually do things (override a model method etc) the Magento way.
Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 11 years ago.
Improve this question
I'm looking for a hosted platform for managing comments on my website.
I came across http://disqus.com/.
Disqus seems to be feature rich, with on my top list requirements support for SEO friendly comments.
So I check many website using Disqus and I cannot find any of theme have friendly SEO comments.
For SEO friendly I mean that comments should be considered plain text and be visible in the HTML source page.
Also I notice that Disqus works only with JAVASCRIPT enabled.
Do you know if the SEO feature for Disqus it is really working and how?
Most important I need this SEO feature working in Universal Code, I use a custom CMS.
The problem with Disqus is that it uses JavaScript to render comments, so, when robots come to your site, they don't find the comments. Even if it uses index-friendly "#!" URLs, those are still not your page, so, they're not applicable here.
They have a REST API you can use. My idea here is to bring all comments from API by code and write it to HTML inside one container then hide this container via JavaScript (not CSS, as I'm not sure whether robots will hate that, but JS is not discover-able).
Then I'd still have the Disqus JS widget, because the API won't bring me all the nice features Disqus direct use has. When a user adds a link, it won't be added to hidden HTML until the page is refreshed, but who cares, it's hidden anyway, Disqus will update their JavaScript and comment will be visible.
The down-side of course is the user is now downloading the comments twice. You can solve this too by doing some checks for request user-agent string or whatever to tell whether the page is requested by robot or not, and display the comments from the API in HTML only in this case (and then you won't even care about hiding it).
Of course there is a trade-off between time implementing this and how effective-nice it can be, but it's at least achievable.
...
P.S. I also heard the WordPress and Drupal plugins render HTML too in addition to JS. So, if you develop semi-dynamic or CMS websites on top of any of them, you can get that already. See Getting Disqus html code to show in source for SEO purposes.
The fact that Disqus script loading the content via AJAX will be less of an issue soon, because Google starts crawling and indexing such content.
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 3 years ago.
Improve this question
SHORT QUESTION
If you want to skip the details below, here's the short question:
I want to know if you keep your app's specifications similarly, in a bugtracker + a wiki and how do you split the information for good management. I look for a simple solution or just a point to start.
DETAILS
I need to keep track of the features for a web app that I want to build. So, I've used MediaWiki to gather a list of features.
For each feature, I have a wiki page where I include functional specs, technical specs and various related brainstormings in FreeMind format or plain text. Also, I include a series of open-questions related to it as TODOs and lots of images for various use cases. I found the wiki to be an excellent place where to keep all these.
I have a page in the wiki with all features transcluded manually so I can see them all in one page, in a specific format.
I also have a page in the wiki where I state what's the goal for v1.0, and a manually transcluded list of features for this version.
In the bug tracker(I use ClockingIT), I want to keep track of the tasks, bugs, etc. in order to build version 1.0 of the product.
ISSUE
Since I keep all features(well, the major features at least) in the wiki, I now feel the need to duplicate them in the bug tracker. Also, after brainstorming on V1.0, I realized there are many smaller features(that are too small to include in the wiki) that I'll need to keep track of in the bug tracker.
The problem is that I end up with 2 systems that will keep and manage the set of features and lots of duplicates will appear, like:
which features get in V1.0 -> this exists in the wiki as a page and the bugtracker keeps a milestone for this; moving a feature from v1.0 to another version, will mean to update both the bugtracker and the wiki
in the bugtracker I add comments as logs for what I do while working on the feature, so the wiki will get deprecated because some part of the brainstorming moves into the bugtracker
the wiki will tend to contain the major features while the bugtracker will contain minor features(like add a button to show/hide a section or something)...but the limit between major and minor features is very subjective and will tend to get messy so I'll have a hard time searching for a feature - I'll have to search in both wiki and bugtracker or I'll have to remember if it was a major or a minor feature
QUESTION
Since I need to keep the features in the wiki because it is an excellent tool for brainstorming, information keeping, etc. what should I include in the bugtracker? How can I efficiently separate these two tools' functionality so they integrate well with each-other and I don't get to duplicate any(or small amount of) data?
Thank you!
I use something mixed. On the wiki, there is a requirements page (among other pages), which describes the features and delivery data. Some features has separated topics where design/implementation details are explained. The requirements topic includes links to bugs with a short description of the bug/feature. Not all features are reflected as bugs. All bugs are listed in the current release section, if they are planned to be fixed in that release. A separated link goes to bug-tracking system to show all the bugs for the product (there are many products in the bug tracker). So:
all features, bug fixes are listed on the requirements page under a particular release;
bug tracking system contains bugs found during testing;
there is no exact definition which requests go to the bug tracker and which don't. An external reviewer may report feature requests as tickets in the bug tracker.
the key point is to keep all the requirements together and organized per release.
Maybe there are better ways to organize things, but this one is the simplest to me, and doesn't require lots of time.
You will need to customize for your needs but have you seen trac : http://trac.edgewall.org/.
This will serve many of your purpose. It combines bug tracker with wiki and other aspects.
Trac is an enhanced wiki and issue tracking system for software development projects. It provides an interface to Subversion (or other version control systems), an integrated Wiki and convenient reporting facilities.