This table quickly converts times into seconds for the use in htaccess rules.

#-------------------------------------------
# TIME CHEAT SHEET 2
#-------------------------------------------
# 300 5 MIN
# 600 10 MIN
# 900 15 MIN
# 1800 30 MIN
# 2700 45 MIN
#
# 3600 1 HR
# 7200 2 HR
# 10800 3 HR
# 14400 4 HR
# 18000 5 HR
# 36000 10 HR
# 39600 11 HR
# 43200 12 HR
# 46800 13 HR
# 50400 14 HR
# 54000 15 HR
# 86400 24 HR
#
# 86400 1 DAY
# 172800 2 DAY
# 259200 3 DAY
# 345600 4 DAY
# 432000 5 DAY
# 518400 6 DAY
# 604800 7 DAY
#
# 604800 1 WEEK
# 1209600 2 WEEK
# 1814400 3 WEEK
# 2419200 4 WEEK
#
# 2419200 1 MONTH
# 4838400 2 MONTH
# 7257600 3 MONTH
# 9676800 4 MONTH
# 12096000 5 MONTH
# 14515200 6 MONTH
# 16934400 7 MONTH
# 19353600 8 MONTH
# 21772800 9 MONTH
# 24192000 10 MONTH
# 26611200 11 MONTH
# 29030400 12 MONTH

Increased performance for all websites

• gzip compress files, use either htaccess (quicker) or php (compatable) nb delate is modern gzip
  compressing some file types will cause the file to be larger ie PNG as it is already compress
• optimize images using Smush IT, makes a big diffference. removes useless data and decreases file size
• gzip output from dynamic sites, using php headers
• minify html by removing white spaces
• aggregate and minify CSS files, gzip output
• aggregate and minify JAVA files, gzip output (not inline as they might be placed there for a reason)
• move Javascript(s) to the bottom of the page, usually just above </body>
• use CSS sprites instead of multiple images, a CSS sprite is where all the images are made in to one and called different
• optimize database via phpmyadmin when nessasary, recommended once a week, select all the joomla tables in the joomla database and then select optimize.
• keep images to a minimum
• dont gzip items more than once in a chain
• have a suitable htaccess, to large and it could slow things down
• disable Etags, unless you actually need them they are a waste of time especially in shared server environments
• make sure google analytics is latest version for speed, use asynchronous version
• make sure all you have the latest version of JAVA and scripts

• google prefers expires and set to 1 month

• look at apache redirect and double slash section and make run quicker ie expressions ?*+

  (.*) is really hungry

• joomla recommends output buffering is disabled. this most likely creates a performance increase.

caching will increase a users experience but not increase raw speed for intial visits such as google

• set far future expires headers for files, this will tell the browser until the file expires it does not need to re-download, PHP or htaccess. htaccess is quicker
• set far future expires headers for dynamic content, this has to be done by PHP
• recommend lenght for far future is 7 days minimum, this allows you to change in a short time if you need. when set unless the clients browser is purged or runs out of room this header will be obeyed

performance items applied to a joomla setup

see - http://www.joomlaperformance.com/articles/performance/so_you_want_to_speed_up_joomla_3_14.html

• joomla global cache on, 60 mins, set in global config, i am currently trying JOT Caching instead
  (this a joomla content cache to hold created content)
• page cache on, 60 mins (this a joomla content cache to hold created content)
• all modules should have caching turned on, use global settings (easier to manage later) (this a joomla content cache to hold created content)
• content gzip on, set in global config
• use JFinalizer or JCH Optimizer (currently prefered) for compressing, minimizing and aggregating js and css
• optimize image files with Smush IT, using firebug and YSlow,
• turn on compression of files via htaccess that are not dynamic
• optimize database via phpmyadmin (see notes in above section)
• setup plugin order, can be important, each layer passes process content to the next plugin in the list
• Process all images with Smush IT,
• make sure google analytics is latest version for speed, use asynchronous version
• gzip joomla content see above worth 0.2 - 0.4 on a commercial template and little content, uses PHP
• disable legacy plugin, worth 50ms on code generation with cache on
• optimize database - via phpmyadmin, select all the joomla tables in the joomla database and then select optimize. do this on a regular basis

• - joomla and jot cache do not store headers

Notes

when stuff doesnt work try this

• JCH optimize can break ajax and javascript stuff
• disabled mootools in template settings (doesnt disable joomlas own mootools, must be standard now)
• excluded mootools.js in jch optimizer and shit works. wonder why it worked before, when you swapp pages ssearch box goes gay, and sh404sef 404 errors happen
• dont minify html when using code snippets

caching

• joomla Far Future Expires Headers plugin, this adds the correct expires headers to
  dynamic content (not etags currently), default settings with 1 hour interval, possible 1 week when happy
• configure Far Future Expires in htaccess for files, all media files usually. 1 week when happy, longer is better but has issues

NB:

• google only downloads the html part not images etc..#
• large ip block list is worth about 2 seconds
• large ip list can add 1 - 1.5s per page load
• cache + jcoptimiser worth at least 2 secs
• install cache cleaner, not performance related but when you have made the changes this is iunvaluable to save time
• seems best. yoo phoneix with compress and gzip on. no compression on in htaccess. no gzip on in JCH optimiser, cache header plugin on.
• trying to gzip png files increases load time. optimise images instead
• dont gzip content more than once and ir could cause excessive use

To Do - investigate

• yoo login, search css.php needs adding and aggregating
• htaccess slimming down maybe
• yoo search .JS needs aggregating
• somehow make images sprites
• is sh404sef the quickest
• xmap cache ? set to 15 mins for now
• if i turn on main cache yoosearch css goes mental, disbled module cache no will turn on jch minimise css and js
• if i turn main cache on, the 2 x yoo modules search and login ccc.php references dissapear
• mess with the global cache option and the 2 x yoo modules (currently yoo search cache turned off yoologin cached 15 mins)
• add to tickets for jch optimize option of a htaccess compression similiar to jfinalizer. htaccess is quicker. no compression/gzip compatible compression/htaccess compression which also uses real files which is better.
• install the google toolbar with page rank i think deliver page speed information
• turn on global cache set to 60 mins miniumm
• far future headers should be set to 1 week minimum from what i read. will test

These are the headers that are set for the aggregated file:

• Content-type: text/css or text/javascript
• Expires: set in admin
• Last-Modified: set based on the time file was created in cache
• Cache-Control: Public This enables proxy caching
• Vary: Accept-Encoding This allows both gzipped and normal version of the file to be cached
• Content-Encoding: gzip if that option is selected

Performance Page (other notes)

• benchmark site before optimising (YSlow, WebWait.com, JoomlaPerformance.com, WebsiteOptimization.com)

Cache

• read caching tutorial (on wiki)
• enable and configure joomla cache (possibly jot cache) - http://www.theartofjoomla.com/joomla-caching-explained.html
  (turned on, either from Global Configuration or enable the "System Cache" Plugin from Plugin Manager. Sometimes enabling Cache does not go well with cyrillics or special characters used)
• Turn on page and module caching.
• set HTTP Cache Headers for joomla dynamic content, use "set max-age= , public , must-revalidate" (check the actual function of this as confilcting reslts)(possibly use private on shop sites)
• configure server/file cache via htaccess - http://www.mnot.net/cache_docs/

HTML Output

• CSS, combine, minify and gzip
• Java Script, combine, minify and gzip
• move/defer all Java Script to bottom of the page
• Minify HTML
• Combine background images in to a css sprite
• Make sure there aren't any Javascript issues like duplicate scripts, or clashing javascript frameworks. can cause slow performance
• Enable joomla gzip for HTML output (Site->Global Configuration->Sever->Enable GZip Compression) to test http://www.gidnetwork.com/tools/gzip-test.php

Other

• configure plugin order
• optimize image files using smusit (reduces size)
• remove unused extensions. possibly better to uninstall extension
• Check for leftover database tables of old components or plugins and drop those tables.
• Optimize and repair the database tables. Use PhpMyAdmin for this. Or 'Admin Tools from Akeeba, Databse Optimise Plugin
• Remove/solve 'Not Founds' or '404' errors they have bad effect on speed. The server/ browser is left thinking about how to deal with this missing item
• use optimised template
• Turn off Joomla error reporting off.
• htaccess performance options:
  Enable HTTP Cache Headers
  Enable gzip options
  Disable ETags (for better performance on clustered servers), unless you need them turn them off

• dont gzip jpg and png because it makes them bigger ? (check this)

Which Parameters are Important?

1. HTTP requests
2. Total size
3. Number of HTML / CSS images
4. Number of CSS / JS (scripts) files.
5. Size of CSS / JS / HTML images.
6. Check for duplicate JS files.
7. Check for NOT FOUND items.

PHP Compression

compressing a websites output makes the delivery of the content to the browser quicker.

Caching

• The fact is that proxy and browser caches will be used whether you like it or not. If you don’t configure your site to be cached correctly, it will be cached using whatever defaults the cache’s administrator decides upon.
• Validators are very important; if one isn’t present, and there isn’t any freshness information (Expires or Cache-Control) available, caches will not store a representation at all.
• HTTP 1.1 introduced a new class of headers, Cache-Control response headers, to give Web publishers more control over their content, and to address the limitations of Expires.
• ETags are made out of three components: the INode, MTime, and Size.
• Removing ETags & Adding Far Future Expires headers is better. ETags require server responses
• Expires Header - Set a particular time and date when the content will expire, header HTTP date is Greenwich Mean Time (GMT), not local time
  - reponse to this is last accessed or lasst modified
  - ie server rule 2 weks from last modified, 2 weeks from last acssessed, date this sets the expires header

• Basically most images, css, javascript, and other files can be optimized for faster download by telling your site visitors to cache them for a certain period of time. The default behaviour is to check the last-modified and/or the Etag headers of the file EVERY time it is requested.

• So a user goes to /home/index.html, and the browser caches all the images and files. Then the user leaves the site and comes back later, and the browser has to send If-Modified-Since conditional GET requests for every cached item, basically to see if the file has been changed and if they should update their cache.

• Dynamic content cannot be cached via htaccess, ie joomla unless you add the headers to the output via php

• When files are then cached by your site visitors they do not send the If-Modified-Since until the set cache time has completed.

• Once an item is cached it will remain cached until it expires or gets revalidated

• The Expires and cache-control headers can’t be circumvented; unless the cache (either browser or proxy) runs out of room and has to delete the representations

• the cached copy will be used until then which means less http requests

• Expires/max-age are superior as they mean there's no need for a request. However, ETag/Last-Modified is still better than nothing.

• less http requests

• ETag and Last-Modified headers are on by default

• BE WARNED. Do not set to long a expire time

• YSlow has a minimum far future date - to be added here soon i think it is 1 week google is 1 month and wants expires

The Relevant Cache-Control Headers are:

Cache-Control : max-age = [delta-seconds]
Modifies the expiration mechanism, overriding the Expires header. Max-age implies Cache-Control : public.

Cache-Control : public
Indicates that the object may be stored in a cache. This is the default.

Cache-Control : private
Cache-Control : private = [field-name]
Indicates that the object (or specified field) must not be stored in a shared cache and is intended for a single user. It may be stored in a private cache (ie browser cache).

Cache-Control : no-cache
Cache-Control : no-cache = [field-name]
Indicates that the object (or specified field) may be cached, but may not be served to a client unless revalidated with the origin server.

Cache-Control : no-store
Indicates that the item must not be stored in nonvolatile storage, and should be removed as soon as possible from volatile storage.

Cache-Control : no-transform
Proxies may convert data from one storage system to another. This directive indicates that (most of) the response must not be transformed. (The RFC allows for transformation of some fields, even with this header present.)

Cache-Control : must-revalidate
Cache-Control : proxy-revalidate
Forces the proxy to revalidate the page even if the client will accept a stale response. Read the RFC before using these headers, there are restrictions on their use.

Caveats

• HTTP/1.0 has minimal cache control and only understands the Pragma: no-cache header. Caches using HTTP/1.0 will ignore the Expires and Cache-Control headers.
• None of the Cache-Control directives ensure privacy or security of data. The directives "private" and "no-store" assist in privacy and security, but they are not intended to substitute for authentication and encryption.

Notes

• "max-age" value indicates the time difference (in seconds) after which the content will be expired and reloaded from the server

• "public" keyword presence indicates that any system along the route may cache the response

• "must-revalidate" indicates caching systems to obey other header information you may provide at a later time about the cache. This should help preventing stale caching (that is, caching that delivers content that is outdated).

• by eliminating the Last-Modified and ETags headers, you are eliminating validation requests, leading to a decreased response time. This should work fine in most cases when dealing with static, rarely updated content.

  Example 1

  http://tutorialpedia.org/tutorials/Apache+enable+file+caching+with+htaccess.html

  Example 2

  http://linuxdevcenter.com/pub/a/linux/2002/02/28/cachefriendly.html?page=2

• The reason I remove and disable the ETag is because supposedly some browsers will ignore your Expires header when it’s present:

• The reason I remove the Last-Modified header is for the same reason:

• The reason I set the Cache-Control header to ‘public’ is so the browser will cache media over HTTPS (see tip #3):

• The reason I set the Cache-Control header to ‘no-transform’ is to prevent proxies from modifying my content.

• Vary: Accept-Encoding response header. This instructs the proxies to cache two versions of the resource: one compressed, and one uncompressed.

Headers

Example

Header unset Server
Header unset Last-Modified
Header unset Date
Header unset Accept-Ranges
Header unset Content-Length
Header unset Keep-Alive
Header unset Connection
Header unset Content-Type
Header unset Cache-Control
Header unset Expires
Header unset Pragma:

When I uncomment my changes, then I get the full header:

HTTP/1.x 200 OK
Date: Wed, 17 Sep 2008 19:37:42 GMT
Server: Apache
Last-Modified: Wed, 17 Sep 2008 15:30:07 GMT
Accept-Ranges: bytes
Content-Length: 58
Keep-Alive: timeout=15, max=100
Connection: Keep-Alive
Content-Type: text/html

Last-Modified Header

• The Last-Modified header allows validation based on the component's timestamp

• Removing this reduces HTTP requests and disables this type of cache header

• The most common validator is the time that the document last changed, as communicated in

• Last-Modified header. When a cache has an representation stored that includes a Last-Modified header,

• it can use it to ask the server if the representation has changed since the last time it was seen, with an If-Modified-Since request.

• if this header is present the browser checks back to the server that is has not been changed and then it uses the cached version

Last-Modified and Cache Control (No Expires set, i think)

• Server sends Last-Modified header with datetime value that means the time when content was changed last time.
  
  Cache-Control: must-revalidate
  Last-Modified: 15 Sep 2008 17:43:00 GMT
  
  
• The first header Cache-Control: must-revalidate means that browser must send validation request every time even if there is already cache entry exists for this object. (because no Expires set)
• Browser receives the content and stores it in the cache along with the last modified value. Next time browser will send additional header:
  
  If-Modified-Since: 15 Sep 2008 17:43:00 GMT
  
  
• This header means that browser has cache entry that was last changed 17:43.
• Then server will compare the time with last modified time of actual content and if it was changed the server will send the whole updated object along with new Last-Modified value.
• If there were no changes since the previous request then there will be short empty-body answer:
  
  HTTP/1.x 304 Not Modified
  
  
• And browser will use the cached content.
• What if server doesn’t send Cache-Control: must-revalidate? Then modern browsers look at profile setting or decide on their own whether to send conditional request. So we better to send Cache-Control to make sure that browser sends conditional request.
• If we still want Last-Modified header (On its own) for static files and the user presses Refresh button, then the browser will send conditional request and the server will respond
  
  “304 Not Modified”.
  
  
• If you disable both Last-Modified and ETag browser will have to download the whole content again when user presses Refresh.

Etags

• The problem with ETags is that they typically are constructed using attributes that make them unique to
• a specific server hosting a site (maybe a specific inode). ETags won't match when a browser gets the original component from one
• server and later tries to validate that component on a different server, a situation that is all too common
• on Web sites that use a cluster of servers to handle requests. ie SHARED HOSTS (or load balanced servers where they do not sync etag data)
• If you're not taking advantage of the flexible validation model that ETags provide, it's better to just remove the ETag altogether
• Remove Etag headers for better performance on clustered servers, and if using joomla because of dynamic content
• Removing the ETag reduces the size of the HTTP headers in both the response and subsequent requests
• By removing the ETag header, you disable caches and browsers from being able to validate files, so they are forced to rely on your Cache-Control and Expires header.

SEO section

Aet in menu

• page title = <h1>
• show title = <h2>

Article options

• show title = <h2>
• but menu item overrules it
• you can set this option in the article aswell for the times it is not used as a menu itme but present in a blog layout

Other notes

• 1024 screensize = 960px visible in browers (because of the browser window size and scroll bars etc...)
• if you use a weired url modified like jsecure lite the module hover links will not work becasuse they point to the admin directory
• disable forgot your password and forgot your username options via menu item (not possible)
  • requires html overiding
  • http://forum.joomla.org/viewtopic.php?f=615&t=795467&p=3007388&hilit=disable+forgot+password#p3007388

• Standalone Applications must have their own folder, use all lowercase.

  Via ftp, create a folder ../sp/
  All standalone applications must have their own nested folder ../sp/othercms/
  Add a .htaccess folder to ../sp/ to deny access to the folder and sub folders (or appropiate - check)

Editing

• JCE is now my prefered editor because ckeditor etc.. have many issues/bugs. i need to either use <pre> or [code] in future to prevent editor stripping
• add to ideas, media manager available in front -end (off by default), ability to delete articles in front end properely/empty trash. the reson for this is a lot of small sites with a couple of pages the users only ever want to alter a few things on their site and do not need to know the back end
• file amamgers eXtploer, Profiles, FILEman (C)
• http://extensions.joomla.org/extensions/core-enhancements/file-management/24160
• how to configure jcs to sort word content
  http://www.joomlacontenteditor.net/support/forum/copy-paste-issues-from-word-2010-to-jce-231
• also read
  http://www.joomlacontenteditor.net/support/forum/problem-pasting-from-word-2013

JCE Suggestions to send

• no ability to easily do margin: 0px auto; as you can either set all margins or individually

Joomlashine suggestions to send

• send to joomla shine
• add tick to unicons

Gallery Notes

• simple image gallery = basic plugin, no captions, responsive
• simple image gallery pro = plugin based gallery + captions - quite good
• joomgallery = complex gallery but not 100% responsive (use 2 column to get around this. this gallery is all editable by the client

how to rip a website page courtesy of customers

• copy and paste whole thing into a word document
• then copy and paste that in to JCE editor and it will strip the junk out
• edit images as needed
• done

Front end editing related

• create article front end
  http://www.cloudaccess.net/joomla-3-0/98-menu-manager/548-create-an-article-menu-item-joomla-3-0.html
• front end only editing is ideal for those who will never change the layout (ie blog style)
• backend editing is requied for those who have a blog layout list page because joomla does not allow deleting from front end except via trashed option. joomla also does not allow media manager access from front end
• need to add a frontend file amanger or add a better file amanger than the inbuilt one. (ie JCE editor or those other ones I found)
• image only sites only require jce which can delete and upload images. sites that need to use other things like pdfs or change the sliders thing can use the in built media manager (orone of the following media managers). front end media managing seems to be a problem
• delete article http://stackoverflow.com/questions/17918784/joomla-3-1-front-end-editing-deleting-and-article
• cannot really delete an article from front end but only change its status to trashed

Joomla Module ACL suggestions

Send this to that guy who did the module acl

• bug/feature - you cannot edit a module from font end unless that permmision is on, iheritance does not work to custom group
• in admin make editable.non edtable modules more contrasted
• allow editing of modules in thefrontrend properely like artilce, at the leat once you finbish editin a module you should be returned to the page you were editing
• in acl allow.disallow sort ordering
• ability to hide non editable module (possibly in acl) resaon is customers can still magle module orders
• possibkly acl allow module posistion change

Other

• Location of system icons - http://quantumwarp.com/media/jui/img/glyphicons-halflings.png
• Turn on Error Reporting properely - in php.ini(there is also a specifc joomla setting in xampp)
  ; XAMPP: Turn display_startup_errors = Off here for a full Joomla support
  display_startup_errors = On
• Database Notes - make sure you use mysqli (innodb tables)
  http://www.joomlaxe.com/article/62-use-mysql-or-mysqli-for-your-joomla.html

• all primary changes are done manually in the files within the template folder and then can be selected.
• settings made, ie default profiles etc, seem to be stored in the database.
• the blank tempate has the very minimum skeleton in it so it can from the outset be used as a template in joomla and then customised. the themes are there as an example.
• the core skeleton is kept in the plugin
• always overide

the folders structures is as follows

• blocks - additional lumps of code called by the core
• core - preset layouts, themes profiles are here, possible also themes that are uploaded
• css - the various css files required
• html - the module/component template overides
• images - image files
• info - unsure, but it is a T3 framework thing rather than the theme directely
• js - required java files, i am not sure if they have to be called or autoloadif in this folder
• local - same layout as core but no files, this is probably where custom files are uploaded

the rest of the files are template specific for obvious reasons

Theme Notes

nb the default theme images are in the image directory, so the themes as mentioned are probably overides

- the real base theme is located in the T3 system plugin
....htdocs\plugins\system\jat3\base-themes\

you put the files in the same folder in the theme directory and it overides it

priority for template files
T3 system plugin --> blank template core files --> custom created template files

a useful overview + block overide
http://www.joomlart.com/forums/showthread.php?48230-Why-so-complex...-and-can-I-override-the-skeleton-of-the-layout&s=3b031bce7ea95b7fefa1c893c42f712d

http://wiki.joomlart.com/wiki/JA_T3_Framework_2/Guides
http://wiki.joomlart.com/wiki/JA_Template_Framework/Guides
http://wiki.joomlart.com/wiki/JA_Template_Framework/FAQs

nb block overides per template (not sure how you would overide rtl (maybe this is done by the plugin)

to view stuff
/?t3info=1&allblocks=1&content=0

this loads all the modules
D:\Documents\websites\joomla\htdocs\plugins\system\jat3\base-themes\default\page\default.php (default) or one of the others if specified

nb footer is a module posistion

to create a new module posistion - easy instruictions
http://www.joomlart.com/forums/showthread.php?45746-Creating-new-module-positions-in-T3

these files open for developing
D:\Documents\websites\joomla\htdocs\templates\ja_t3_blank\page\default.php (main layout)
D:\Documents\websites\joomla\htdocs\templates\ja_t3_blank\css\template.css (default blank template css) NB i copied this to the blank template first before editing
D:\Documents\websites\joomla\htdocs\plugins\system\jat3\base-themes\default\css\template.css (main default css in system plugin default base theme)
D:\Documents\websites\joomla\htdocs\templates\ja_t3_blank\local\themes\lancastrian\css\template.css (my custom theme css)

nb - check for overidedes backwards. ie check lacastrian it css, then the blank template css and then the system plugin default css

header gets added here
<a name="Top" id="Top">

see lD:\Documents\websites\joomla\htdocs\templates\ja_t3_blank\core\etc\layouts\default.xml it is defined in there

overides
these only work on specific atrribvutes of a thing, not the whole decleration.

Locations for setting permissions

• (system/Global configuration/Permissions) - this is where the absoulute base settings are and from which inheritence starts
• Users - all permissions need a user at some point to work and to be applied to
• User Groups (Users/Groups) - all users are assigned to a user group. A user group can be nested. in fact all user groupos are nested from 'Public'. It is user groups that get the permissions assigned to them and NOT users
• Access levels (Users / Access Levels) - these are for menus, modules and possibly plugins (not compoenents) ie simpler stuff in joomla
• compoent permissions (System/Global Configuration/{compeonet menu on left} or open the compoenent up and click on the options button at top right) - you can set permissions here at the compeoent level rather than further up the tree, this can be done for every user
• group
• in the modules (3.2+), there is now a permissions tab

Video notes

• administrator vs super user , super user can access global joomla config
• http://docs.joomla.org/User_Group_Access_levels_explained_in_simple_terms
• there are 2 basic ways to configure permissions per groups

1. take a group and then remove permissions
2. start with nothing and add permissions in

• If you create a new group it will inherit the permissions from its parent
• manager is a good groupt to just give access to the content items by default but has the slight downside of exposing other stuff i dont want the client to see or mess with. so with manager i would need to disable options.
• when assigning a group to a user you only need to select the group at the end of the tree because it is inheriting the permissions of its parents anyway.
• In user manager options, there is an option to set a group to being a guest usergroup. this is where the item/module is display whilst public and then when logged in dissapers. (56:38)
• the admin menu will automaticall hide stuff that is not required
• The Public group is the parent of all other groups
• super user option (in permissions) is basically ability to configure the component
• you can create new articles from the frontend via a menu item and in this menu item you can specify the category it will appear in.

The following are instructions on how to transfer a .com address through WHMCS.

This is what the client sees when a .com domain is transfered in to your hosting company, intiated at your end.

23-07-14 18:03

Once the process is started, the new hosting company has requested a transfer, the Owner/Domain admin receives the following email where he must click on the link to start the process.

Subject: Domain Transfer Request for OxxxxxxSERVICES.COM

STANDARDIZED FORM OF AUTHORIZATION

DOMAIN NAME TRANSFER - Initial Authorization for Registrar Transfer

Attention: Building Company
Re: Transfer of OxxxxxxSERVICES.COM

eNom, Inc. has received a request from Bob Builder (www.webhosting.co.uk) on 
23 Jul 2014 to become the new registrar of record.

You have received this message because you are listed as the Registered Name 
Holder or Administrative contact for this domain name in the WHOIS database.

Please read the following important information about transferring your domain 
name:

* You must agree to enter into a new Registration Agreement with us.  You can 
review the full terms and conditions of the Agreement at
< http://transfer-approval.com/u.asp?id=A3C51141-CFF9-47B6-95C5-5DC00EBB77CF >

* Once you have entered into the Agreement, the transfer will take place within 
five (5) calendar days unless the current registrar of record denies the 
request.

* Once a transfer takes place, you will not be able to transfer to another 
registrar for 60 days, apart from a transfer back to the original registrar, in 
cases where both registrars so agree or where a decision in the dispute 
resolution process so directs.

If you WISH TO PROCEED with the transfer, you must respond to this message by 
using the following URL (note if you do not respond by 30 Jul 2014, 
OxxxxxxSERVICES.COM will not be transferred to us):
< http://transfer-approval.com/u.asp?id=A3C51141-CFF9-47B6-95C5-5DC00EBB77CF >
YOU MUST CLICK THIS LINK TO CONTINUE THE TRANSFER PROCESS

If you DO NOT WANT the transfer to proceed, then don't respond to this message.

If you have any questions about this process, please contact 
info@webhosting.co.uk.

23-07-14 18:43

The following is a screenshot  of what you will see once the link above is clicked

23-07-14 18:55

A further email is sent, also with a link in it to click on. This email is slightly different as it provides a code to be entered on the new webpage to confirm the domain move.

Subject: Transfer Away request has been received for the domain  oxxxxxxlservices .com

An English version of this message is contained below.


Attention: onexxx@aol.com

Re: Transfer of oxxxxxxservices.com

Tucows received notification on Wed Jul 23 13:51:27 2014 that you have requested a transfer to another domain name registrar.

If you want to proceed with this transfer, you do not need to respond to this message.

If you wish to cancel the transfer, please contact us before Mon Jul 28 13:51:27 2014 by going to our website,

https://approve.domainadmin.com/transfer/?away=1&domain=oxxxxxxlservices.com&id=RT2AKb4SC7 to confirm.

You may need to enter the following information to accept or decline the transfer:

     Domain Name:  oxxxxxxservices.com
     Transfer Key: RT3AKb4SC7

If we do not hear from you by Mon Jul 28 13:51:27 2014, the transfer will proceed.

23-07-14 20:17

On this page you must now choose to accept or decline the transfer.

Done

The Problem

I have installed projectfork and installed the PF Menu module. I am using SEF (native not extension). All the links are as follows

http://www.mysite.com/dashboard
http://www.mysite.com/projects
etc..

as you can see they are all root links, but i would like them like

http://www.mysite.com/projectfork/dashboard
http://www.mysite.com/projectfork/projects

On the docs site, the menus on the left do exactly this.
http://projectfork.net/docs

Are all the docs menus actually part of the main menu or is there a joomla trick i can use ie hidden menu item to get all the PF module menu to have 'normal' links

thanks

Solution

My method allows me to have all my projectfork links in the projectfork subfolder. With the standard install of PF and joomla. The PF Menu Module Links are all root items. I wanted my in a subfolder as if i had installed a seperate piece of software whilst everything else was kept route.

Install projectfork

• this install PF, modules and the menus

Make the following changes:

PF Menu

• edit the PF menu
• add a menu item, call it 'projectfork' point it to the PF dashboard
• in the PF menu select all the other items and select batch (at the top)
• move all the items under the new 'projectfork' menu item you have just created

Main Menu

• create a menu item, call it 'projectfork' or what ever you want, do not fill in alias
• select menu item type 'Menu Item Alias', this is under 'System Links'
• point the 'Menu Item Alias' to the top level menu item in the PF Menu
• save

PF Menu Module

• edit the PF Menu Module called 'Projectfork'
• set 'Base Item' to 'Projectfork' (or what ever your parent menu item is in the PF Menu)
• set the start level = 2

You have now configured all your PF links to be under the directory projectfork.

Other methods of getting a menu to the url you want

• Add to main menu (the traditional method)
  - move the PF menu items from the PF menu to the Main Item whilst giving it a parent item which will then provide the url structure you want
• Leave PF Menu in a standalone Module
  - If you want the PF Menu module left as is, in a separate module. Just give it a parent item, this parent item is best pointing to the Front dashboard. The downside of this if it has to be dispalyed all the time. You can then go further and hide the parent item. The menu will then look exaclty the same as it was when it was installed but with a url prefix (ie projectfork/dashboard)
• Publish PF menu next to main menu
  - as above but publish the module to the main menu slot, it should then create a menu but next to the regular menu. The advantage of this is the url structure you want is created, the menu is maintained spearately.

If your login box is in this position, joomla is in debug mode.

I would like to create a Submenus from a item but they not have alias in URLs. Similar than this:

Parent item: "Market" and URL: "www.mydomain/market"
Submenu item menu: "Cars" and URL: "www.mydomain.com/cars"

Now this is same than this

Parent item: "Market" and URL: "www.mydomain/market"
Submenu item menu: "Cars" and URL: "www.mydomain.com/market/cars"

How can I do to do not add parent alias (bolded text) in submenu item?

Solution

With this method you can manually create Joomla menu items with almost any URL you want

• Create a new Menu (NOT Menu Item) say Hidden Menu
• In the Hidden Menu, create a new menu item Cars
• In the Main Menu, under the menu item Market, create a new menu item Cars of the type Menu Alias and point this menu item to the menu item Cars in the menu Hidden Menu

Article Taken from here

Sometimes you want to create a link to a menu item, but you do not want a menu item.

You can link directely with the ugly internal joomla link but no-one wants that. To get around this, there is a trick.

• create a new menu and call it 'Hidden Menu Links'
• create a link in this menu to the item you want
• in your article or Custom HTML, add a JTree link and select the 'Hidden Menu Links', select the link yoou want, and there you go.

NB:

• If the menu item's alias is contact-us you could just use /contact-us as a normal link but this will not have all the benefits of a joomla JLink
• in joomla 3.0x the 'Hidden Menu Links' module is not required, everything relates to the 'Hidden Link Menu' and it's permissions
• Joomla Article Link With No Visible Menu Item - YouTube