Joomla! Documentation - User contributions [en]

J1.5:Database structure

2009-11-30T16:25:16Z

Mpn 1983:

{{stub}}
==Structure==
The J! 1.5.x database structure includes 36 Tables
Tables listing w/out prefix_
#banner
#bannerclient
#bannertrack
#categories
#components
#contact_details
#content
#content_frontpage
#content_rating
#core_acl_aro
#core_acl_aro_groups
#core_acl_aro_map
#core_acl_aro_sections
#core_acl_aro_groups_aro_map
#core_log_items
#core_log_searches
#groups
#menu
#menu_types
#messages
#messages_cfg
#migration_backlinks
#modules
#modules_menu
#newsfeeds
#plugins
#polls
#poll_data
#poll_date
#poll_menu
#sections
#sessions
#stats_agents
#templates_menu
#users
#weblinks

'''API table Relationships joomla 1.5'''

#Lien : http://www.torkiljohnsen.com/wp-content/uploads/2006/04/joomla_15_database_schema.png

#[[Detailed list of fields]] [[Category:Database]]

J1.5 talk:Database structure

2009-11-27T17:09:57Z

Mpn 1983:

This is one of our principal "landing pages" identified from the Google Analytics data. I think you need to think about what information people are looking for when they type "Joomla database" into their search engines. I would suggest that you start off with an introduction (that we can re-use as a glossary entry), then mention which databases we support (basically just MySQL at the moment). Then add links to further documentation like the DB schema, descriptions on individual tables, links to the API reference, how-to's on using the database API classes/methods and so on.

== A request ==

Could the new documentation please provide explanation of the three letter acronyms used in the database names?

Tony Davis 08:29, 9 March 2009 (UTC)

--------------
I am new to Joomla!, and am trying to understand its capabilities regarding forms and databases. Searching "database" in the wiki search box, I landed at this page, with no other results listed, nor links from this page to other useful pages about Joomla & databases. A more general, useful search result from searching "database" would have been the http://docs.joomla.org/Category:Database page. Perhaps a link to that could be added in a "see also" list at the end of this page.

cowboyjo 11 Apr 2009

--------------

This page and the one on the list of fields seem unnessacery?

Who is it aimed at? anyone installing Joomla would have needed to get a database created and anyone making changes to the database structure are likely to be devs that would know how to find the structure of the database using something like phpmyadmin or just the sql explain statement?

Also the DB gets new tables added to with almost every extension installed and unless this structure has been taken from the 1.6 vanilla install then it is probably going to change for that. (is that an issue?)

--[[User:Mpn 1983|Matt Newman]] 17:09, 27 November 2009 (UTC)

--------------

Making your site Search Engine Friendly

2009-11-27T16:52:13Z

Mpn 1983:

{{cookiejar}}

== Why create a Search Engine Friendly Site? ==
To start off this article, I want to give an answer to this question. If your Web site is anything like mine, then your biggest visitor is an engine bot. In order to add your page, a search engine (like Google) will send out "crawlers" or "bots" to harvest your pages. These bots cannot harvest things that are created/triggered by javascript, or 'see' images (though they do check alt tags) and don't play well with flash files if at all. While all these things may make the site look better, they do little to nothing in terms of SEO (search engine optimisation).

== Keywords ==
{{stub|section}}
More about keyword density than the meta tag which is largely ignored by large search engines.

== Use Semantic HTML ==
{{stub|section}}
Use semantic HTML - only 1 H1 per page for the most important header etc.

== Use links in your content ==
{{stub|section}}
Have good links inline in text (articles) and avoid the use of things like 'click here' as the text that displays for a link. You want to try and have something that conveys the gist of the content of the page that the link points to.

== Have a structured or planned navigation ==
{{stub|section}}
having a good navigation system is hugely beneficial for allowings bots to effectively crawl your site. (joomla goes a long way for doing this for you when used correctly so thats a big bonus).

== Have a sitemap ==
{{stub|section}}
Sitemap?

== Things to remember ==
{{stub|section}}
That anything that requires a login will not be 'seen' by a search engine. 
That this article only just starts to scrape the surface. 
That frequent maintenance and updates are a big part of SEO. 
That SEO is only the start - it might help people find your site through search engines but you've got to work out how to get them to stay or come back or use your site.

Making your site Search Engine Friendly

2009-11-27T16:49:46Z

Mpn 1983:

{{cookiejar}}
{{stub}}

== Why create a Search Engine Friendly Site? ==
To start off this article, I want to give an answer to this question. If your Web site is anything like mine, then your biggest visitor is an engine bot. In order to add your page, a search engine (like Google) will send out "crawlers" or "bots" to harvest your pages. These bots cannot harvest things that are created/triggered by javascript, or 'see' images (though they do check alt tags) and don't play well with flash files if at all. While all these things may make the site look better, they do little to nothing in terms of SEO (search engine optimisation).

== Keywords ==
More about keyword density than the meta tag which is largely ignored by large search engines.

== Use Semantic HTML ==
Use semantic HTML - only 1 H1 per page for the most important header etc.

== Use links in your content ==
Have good links inline in text (articles) and avoid the use of things like 'click here' as the text that displays for a link. You want to try and have something that conveys the gist of the content of the page that the link points to.

== Have a structured or planned navigation ==
having a good navigation system is hugely beneficial for allowings bots to effectively crawl your site. (joomla goes a long way for doing this for you when used correctly so thats a big bonus).

== Have a sitemap ==
Sitemap?

== Things to remember ==
That anything that requires a login will not be 'seen' by a search engine. 
That this article only just starts to scrape the surface. 
That frequent maintenance and updates are a big part of SEO. 
That SEO is only the start - it might help people find your site through search engines but you've got to work out how to get them to stay or come back or use your site.

Making your site Search Engine Friendly

2009-11-27T16:46:58Z

Mpn 1983:

{{cookiejar}}

== Why create a Search Engine Friendly Site? ==
To start off this article, I want to give an answer to this question. If your Web site is anything like mine, then your biggest visitor is an engine bot. In order to add your page, a search engine (like Google) will send out "crawlers" or "bots" to harvest your pages. These bots cannot harvest things that are created/triggered by javascript, or 'see' images (though they do check alt tags) and don't play well with flash files if at all. While all these things may make the site look better, they do little to nothing in terms of SEO (search engine optimisation).

== Keywords ==
More about keyword density than the meta tag which is largely ignored by large search engines.

== Use Semantic HTML ==
Use semantic HTML - only 1 H1 per page for the most important header etc.

== Use links in your content ==
Have good links inline in text (articles) and avoid the use of things like 'click here' as the text that displays for a link. You want to try and have something that conveys the gist of the content of the page that the link points to.

== Have a structured or planned navigation ==
having a good navigation system is hugely beneficial for allowings bots to effectively crawl your site. (joomla goes a long way for doing this for you when used correctly so thats a big bonus).

== Have a sitemap ==
Sitemap?

== Things to remember ==
That anything that requires a login will not be 'seen' by a search engine. 
That this article only just starts to scrape the surface. 
That frequent maintenance and updates are a big part of SEO. 
That SEO is only the start - it might help people find your site through search engines but you've got to work out how to get them to stay or come back or use your site.

Making your site Search Engine Friendly

2009-11-27T16:44:27Z

Mpn 1983:

{{underconstruction}}
{{cookiejar}}

== Why create a Search Engine Friendly Site? ==
To start off this article, I want to give an answer to this question. If your Web site is anything like mine, then your biggest visitor is an engine bot. In order to add your page, a search engine (like Google) will send out "crawlers" or "bots" to harvest your pages. These bots cannot harvest things that are created/triggered by javascript, or 'see' images (though they do check alt tags) and don't play well with flash files if at all. While all these things may make the site look better, they do little to nothing in terms of SEO (search engine optimisation).

== Keywords ==
More about keyword density than the meta tag which is largely ignored by large search engines.

== Use Semantic HTML ==
Use semantic HTML - only 1 H1 per page for the most important header etc.

== Use links in your content ==
Have good links inline in text (articles) and avoid the use of things like 'click here' as the text that displays for a link. You want to try and have something that conveys the gist of the content of the page that the link points to.

== Have a structured or planned navigation ==
having a good navigation system is hugely beneficial for allowings bots to effectively crawl your site. (joomla goes a long way for doing this for you when used correctly so thats a big bonus).

== Have a sitemap ==
Sitemap?

== Things to remember ==
That anything that requires a login will not be 'seen' by a search engine. 
That this article only just starts to scrape the surface. 
That frequent maintenance and updates are a big part of SEO. 
That SEO is only the start - it might help people find your site through search engines but you've got to work out how to get them to stay or come back or use your site.

Making your site Search Engine Friendly

2009-11-27T16:43:06Z

Mpn 1983:

{{inuse}}
{{cookiejar}}

== Why create a Search Engine Friendly Site? ==
To start off this article, I want to give an answer to this question. If your Web site is anything like mine, then your biggest visitor is an engine bot. In order to add your page, a search engine (like Google) will send out "crawlers" or "bots" to harvest your pages. These bots cannot harvest things that are created/triggered by javascript, or 'see' images (though they do check alt tags) and don't play well with flash files if at all. While all these things may make the site look better, they do little to nothing in terms of SEO (search engine optimisation).

== Keywords ==
More about keyword density than the meta tag which is largely ignored by large search engines.

== Use Semantic HTML ==
Use semantic HTML - only 1 H1 per page for the most important header etc.

== Use links in your content ==
Have good links inline in text (articles) and avoid the use of things like 'click here' as the text that displays for a link. You want to try and have something that conveys the gist of the content of the page that the link points to.

== Have a structured or planned navigation ==
having a good navigation system is hugely beneficial for allowings bots to effectively crawl your site. (joomla goes a long way for doing this for you when used correctly so thats a big bonus).

== Have a sitemap ==
Sitemap?

== Things to remember ==
That anything that requires a login will not be 'seen' by a search engine. 
That this article only just starts to scrape the surface. 
That frequent maintenance and updates are a big part of SEO. 
That SEO is only the start - it might help people find your site through search engines but you've got to work out how to get them to stay or come back or use your site.

Talk:Changing the style according to article section or category

2009-11-26T11:24:20Z

Mpn 1983:

Discussion in Joomla! Forum:
[http://forum.joomla.org/viewtopic.php?f=466&t=219726]

How much PHP can be put into this article? I don't see a way doing it without changing the template's code.

I think, it would be good to add a CSS-File named by the category or category-Id, that will be included by the PHP-Code.

e.g.

'''IF''' the file /template/{templatename}/css/categories/{examplecategory}.css '''EXISTS'''

'''THEN''' include it into Document.

[[User:BenniP|BenniP]] 10:40, 21 March 2009 (UTC)

Apologies if it's poor etiquitte to bring up oldish topics (i've been doing some lightweight dev work for a couple of years but this is my first venture into contributing to an open source project). Also never really used a wiki before (*brushes sand out of hair*). I'm just reading through the documentation and came across this which is something I think i'll need on my next couple of projects.

I agree that I can't see a way of doing this without changing some code somewhere (i.e. not possible just through the use of the admin area + and html+css).

As I currently try use something like minify to gzip the js + css it'd suit me better if the <body> was tagged with classes for the section and category so all css could be applied from one main css file.

So I'll try and look at both solutions.

If I can get my act together i'll have a play with it and then post a link to anything if I can get a reasonably easy (for the admin) working solution. I'll be trying to get involved in a bit of the 1.5 -> 1.6 code cleanup if I can (if i'm capable of doing it) too so I might mosey on over to the 1.6 group and see if they've had any requests to implement somethign like this?

If I haven't posted back within a week it's likely i've not done anything on it and probably won't get a chance.

--[[User:Mpn 1983|Matt Newman]] 11:24, 26 November 2009 (UTC)

J1.5 talk:Developing a MVC Component/Adding Backend Actions

2009-09-24T14:36:47Z

Mpn 1983:

J1.5 talk:Developing a MVC Component/Adding Backend Actions

2009-09-24T14:35:53Z

Mpn 1983:

== Component tutorial - strange behaviour ==

Thanks for the documentation.

Was not sure where to bring up questions about if the actual component itself has an error in it or not. I have started a topic in the forum [http://forum.joomla.org/viewtopic.php?f=303&t=435482]

== Step 6 is very difficult to follow ==

In the last 3 days i've gone through the tutorial from the start. I've been doing website development for a while (2 years) but am new to both Joomla and the MVC pattern. I hand coded everything into my IDE (netbeans) after reading through the article (I'd skim read through once, then go back and try and create the component) steps 1-3 are very simple and easy to follow.

So when I got stuck I went to compare my component with the zipped one supplied... uh huh... they were/are totally different?

Where did the admin 'controllers' folder come from? 
Why is there only 1 controller file in the admin 'controllers' folder this seems redundant and unexplained - surely you only need a folder for controllers if multiple controllers are required? Doing this to the hello example seems to be complicating things unnessecarily.

Having re-read this step several times I don't think it's mentioned in 'Getting Down and Dirty: Doing the Real Work' you should have created the folder 'controllers' in /administrator/components/com_hello/admin (if it is it's certainly not obvious).

Also I don't understand why there is a controllers folder

Step 4 begins to get complex and I think maybe where the root of my trouble with step 6 is (I think it would benefit hugely from the suggestions in: http://docs.joomla.org/Talk:Developing_a_Model-View-Controller_Component_-_Part_4_-_Creating_an_Administrator_Interface#Renaming_Part_4 ).

Step 6 doesn't give enough information about where the new admin files should be created and how they'd be named, it seems to supply source code with too little consideration to context in terms of filepaths. It would probably benefit to being broken down again into smaller parts.

I'll try and actually make recommendations about this in the next week or so (i'm at work at the moment so i'll try and do this from home).

J1.5 talk:Developing a MVC Component/Adding Backend Actions

2009-09-24T14:03:48Z

Mpn 1983:

== Component tutorial - strange behaviour ==

Thanks for the documentation.

Was not sure where to bring up questions about if the actual component itself has an error in it or not. I have started a topic in the forum [http://forum.joomla.org/viewtopic.php?f=303&t=435482]

== Step 6 is very difficult to follow ==

In the last 3 days i've gone through the tutorial from the start. I've been doing website development for a while (2 years) but am new to both Joomla and the MVC pattern. I hand coded everything into my IDE (netbeans) after reading through the article (I'd skim read through once, then go back and try and create the component) steps 1-3 are very simple and easy to follow.

So when I got stuck I went to compare my component with the zipped one supplied... uh huh... they were/are totally different?

Where did the admin 'controllers' folder come from?
Why is there only 1 controller file in the admin 'controllers' folder this seems redundant and unexplained - surely you only need a folder for controllers if multiple controllers are required, if that's true then perhaps an example of when you'd require multiple controllers could be explained?

Having re-read this step several times I don't think it's mentioned in 'Getting Down and Dirty: Doing the Real Work' you should have created the folder 'controllers' in /administrator/components/com_hello/admin (if it is it's certainly not obvious).

Also I don't understand why there is a controllers folder

Step 4 begins to get complex and I think maybe where the root of my trouble with step 6 is (I think it would benefit hugely from the suggestions in: http://docs.joomla.org/Talk:Developing_a_Model-View-Controller_Component_-_Part_4_-_Creating_an_Administrator_Interface#Renaming_Part_4 ).

Step 6 doesn't give enough information about where the new admin files should be created and how they'd be named, it seems to supply source code with too little consideration to context in terms of filepaths. It would probably benefit to being broken down again into smaller parts.

I'll try and actually make recommendations about this in the next week or so (i'm at work at the moment so i'll try and do this from home).

J1.5 talk:Developing a MVC Component/Adding Backend Actions

2009-09-24T13:58:40Z

Mpn 1983:

J1.5 talk:Developing a MVC Component/Adding Backend Actions

2009-09-24T13:58:17Z

Mpn 1983: /* Step 6 is very difficult to follow */ new section

== Component tutorial - strange behaviour ==

Thanks for the documentation.

Was not sure where to bring up questions about if the actual component itself has an error in it or not. I have started a topic in the forum [http://forum.joomla.org/viewtopic.php?f=303&t=435482]

== Step 6 is very difficult to follow ==
In the last 3 days i've gone through the tutorial from the start. I've been doing website development for a while (2 years) but am new to both Joomla and the MVC pattern. I hand coded everything into my IDE (netbeans) after reading through the article (I'd skim read through once, then go back and try and create the component) steps 1-3 are very simple and easy to follow.

Step 4 begins to get complex and I think maybe where the root of my trouble with step 6 is (I think it would benefit hugely from the suggestions in: http://docs.joomla.org/Talk:Developing_a_Model-View-Controller_Component_-_Part_4_-_Creating_an_Administrator_Interface#Renaming_Part_4 ).

Step 6 doesn't give enough information about where the new admin files should be created and how they'd be named, it seems to supply source code with too little consideration to context in terms of filepaths. It would probably benefit to being broken down again into smaller parts.

I'll try and actually make recommendations about this in the next week or so (i'm at work at the moment so i'll try and do this from home).

== Step 6 is very difficult to follow ==

In the last 3 days i've gone through the tutorial from the start. I've been doing website development for a while (2 years) but am new to both Joomla and the MVC pattern. I hand coded everything into my IDE (netbeans) after reading through the article (I'd skim read through once, then go back and try and create the component) steps 1-3 are very simple and easy to follow.

So when I got stuck I went to compare my component with the zipped one supplied... uh huh... they were/are totally different?

Where did the admin 'controllers' folder come from?
Why is there only 1 controller file in the admin 'controllers' folder

Having re-read this step several times I don't think it's mentioned in 'Getting Down and Dirty: Doing the Real Work' you should have created the folder 'controllers' in /administrator/components/com_hello/admin (if it is it's certainly not obvious).

Also I don't understand why there is a controllers folder

Step 4 begins to get complex and I think maybe where the root of my trouble with step 6 is (I think it would benefit hugely from the suggestions in: http://docs.joomla.org/Talk:Developing_a_Model-View-Controller_Component_-_Part_4_-_Creating_an_Administrator_Interface#Renaming_Part_4 ).

Step 6 doesn't give enough information about where the new admin files should be created and how they'd be named, it seems to supply source code with too little consideration to context in terms of filepaths. It would probably benefit to being broken down again into smaller parts.

I'll try and actually make recommendations about this in the next week or so (i'm at work at the moment so i'll try and do this from home).

J1.5 talk:Developing a MVC Component/Adding Backend Actions

2009-09-24T13:00:49Z

Mpn 1983: /* Component tutorial - strange behaviour */