Question: I have just downloaded AutoTweet NG, how do I install it, configure it and authorize it?
Answer: AutoTweet NG is a fantastic component/plugin combo that automatically tweets or posts your status's on Facebook as you create new articles on your Joomla site. We're going to assume you have already downloaded the component.
Step One: Log into the back end of your Joomla site... Click here to read full tutorial.
Question: I am using xmap to generate an xml feed for Bing Webmaster Tools. Bing returned the following error.
HTTP code: 200
Severity: Error Line: 87 Position: 2 Message: The element 'url' in namespace 'http://www.sitemaps.org/schemas/sitemap/0.9' has invalid child element 'lastmod' in namespace 'http://www.sitemaps.org/schemas/sitemap/0.9'. List of possible elements expected: any element in namespace '##other'.
Help.
Answer: The problem is xmap... Click here for full tutorial.
Serr.Biz has posted several new tutorials on the site, dealing with configurations for modules, plugins and a few basic functions of Joomla!
Click one of the following links below to view the tutorial.
For more great tutorials, articles and modules, please visit Serr.Biz!
Question: How do I change required fields in user registration form of Virtuemart?
Answer: The developers of Virtuemart have build this functionality into the core application so it doesn't get much easier than this.
1) Log into Joomla > Components > Virtuemart
2) Navigate to the "Manage User Fields" control panel which is in the left nav links under ADMIN.
3) In the first column to the right of the user fields you have the option to make the field required, or not. Just click anything that has a green check mark and it will turn into an X, which means it is no longer required
Creating a product feed with Joomla, Virtuemart and CSVImproved.
Part 1: Pricegrabber / Yahoo.
In this part of the tutorial series, we are going to show you how to use CSVImproved in conjunction with Virtuemart to creat a proper product feed to upload to Pricegrabber and Yahoo.. For full tutorial please click here.
Out of curiosity, we recently decided to take a look through Google Analytics Mobile. We installed it on our Android phones to test drive some features it seems to offer.
When we first heard about Google Analytics Mobile, we thought it was a pretty cool idea all around. We thought of how useful it would be to have all of our Google Analytics statistics at our fingertips. What if we were to go to a meeting and forgot one crucial report that we printed out back at the office? What if we were speaking to a customer and wanted to show some statistics of our own site as an example but we were not near a computer? No problem, load up Google Analytics Mobile and all of this information is easily accessible anywhere we have a data connection ... Click here for full story
A: From a web development standpoint, it's more of a pain in the rear than it is useful.
Don't get us wrong, it has many features such as built in spell check, tons of plug-ins, fast browsing speeds and very slick minimalistic GUI. However certain aspects of the browser may make coders and webmasters want to pull their hair out more than it will make them say, "That's cool.". Where we gained a few bald patches was during a session of QA testing with VirtueMart and integrating Google Adwords Conversion Tracking.
We had placed a tracking code into a 'Thank You' checkout page of Virtuemart, and upon testing a purchase, we couldn't find the code script we had put inside. We searched and searched through the source code as provided by Google Chrome, double checked our uploads, screamed a few obscenities at the computer, furiously drank a pot of coffee and we still couldn't figure out why in the back end of Joomla, it showed the code, but in the front end on the browser it was nowhere to be found!
We rewrote the code, made some test pages, re-uploaded the changes and once again, no tracking code to be found in the front end upon viewing the source. At our wits end, we then decided to switch browsers.We brushed off the dust of IE8 and viewed the source. Low and behold, we found the tracking code right where it was supposed to be.
So what was the problem? We realized that Chrome displayed the source code differently from Firefox and Internet Explorer. It displays each element in its own separate area, rather than all compiled together in one single window. In order to find the code later in Chrome, after figuring out exactly what the problem was, we found that we needed to select the item in Chrome, click the 'Inspect Element' menu item and expand the element just to find the general area that our code was placed.
Some might say, "But Google is doing that so you can see details of individual code! You can view things in a much more detailed aspect rather than all together.". Agreed, this idea is very cool, however we found that simply viewing the source and being able to do a search for a line of code we're looking for is so much easier than trying to figure out another browsers 'new' and 'cool' way of reinventing the wheel.
Again, don't get us wrong- Google Chrome is a fantastic browser, it has countless options/features and an ease of use for the intermediate to expert web surfer. However for someone who is attempting to bug test or manage a website's issue, Chrome may not be the way to go.
