I started my own little list of my most used functions, anyone else want to share theirs?

All pages I have with a name with spaces in it has a slug(auto created) with underscores, naturally.

Now everything is being treated as a language.

so
I make

My Page

slug becomes
my_page

And i have a new language called
"page" all over the place.

How is this supposed to behave ?
Can I never use underscores in slugs now?
I have to avoid spaces in IDs.
And have to manually set titles now.

Just a little confused, any help appreciated.

Can this be fixed so only valid language codes are recognized as _ appends ?

Comptability: Tested on 3.0+
Version: 0.1 ( Initial Release )
Description: Adds Tagging UI to keyword / Tagging input fields.
Features:

• Easy tag entry/removal, no commas required

• Individual tags can be styled, color coded etc.

• I18n Autocomplete compatible

• Works with I18n Gallery tag fields

Known Issues:

• "add a tag" label disappears after focus

Screenshots:

CSS rules for tags, recommended you use custom admin css plugin.
class = tag_tagname

.tag_green{
 background: #CCFFCC !important;
}

Need testers
Will add to extend after testing.

Future development is planned.

The language is determined by the language in the user session (if previously set with the URL parameter "setlang") and the http accept language header. By using the URL parameter "lang" this can be overridden for the current request.

If you want to show the language in the URL, see here.

Installation

Copy i18n.php to your plugin directory, change the constant I18N_DEFAULT_LANGUAGE in i18n.php, and replace the following functions in your template(s):

• get_component with get_i18n_component

• get_navigation with get_i18n_navigation

Usage

To internationalize a page,

• create another page with the same slug/URL and the 2-letter language code separated by a "_" (e.g. for page "index" create another one "index_it" for italian),

• set its meta data, esp. the title and the menu text.

• The properties "parent page", "template" and "add to menu" are ignored, the properties of the base page (without language) are used instead.

The base page (without language) is assumed to be in the language specified as I18N_DEFAULT_LANGUAGE in i18n.php.

To use the internationalized hierarchical menu,

• ensure that the hierarchical structure of the base pages (without language) is set up correctly (property "parent page"),

• the "add to menu" property of the relevant base pages is checked,

• all language pages have at least the "title" property set,

• add  to your template(s) "get_i18n_navigation(return_page_slug(), minlevel, maxlevel)", e.g.
     

  • "get_i18n_navigation(return_page_slug(),0,0)" for your top level menu in the header, and

  • "get_i18n_navigation(return_page_slug(),1,10)" for the remaining menu levels in the sidebar menu

• for a menu, which should only contain entries, which are available for the current language use "get_i18n_navigation(return_page_slug(),0,10,I18N_SHOW_LANGUAGE)"

• for a site map use "get_i18n_navigation(return_page_slug(),0,10,I18N_SHOW_PAGES)" (all pages, menu texts) or "get_i18n_navigation(return_page_slug(),0,10,I18N_SHOW_TITLES)" (all pages, titles) or "get_i18n_navigation(return_page_slug(),0,10,I18N_SHOW_MENU)" (only the pages visible in the menu).

get_i18n_navigation adds the following css classes to the list items:

• slug of the page

• slug of the page's parent

• "current", if the page is the current page

• "currentpath", if the page is a parent, grandparent, etc. of the current page

• "open", if the page has children whose menu items are currently displayed

• "closed", if the page has children whose menu items are currently not displayed

If you want a one-level menu only, you have to make sure that all your base pages that are in the menu have "--- None ---" as parent.

Problem Solving

If, when visiting the site (with Chrome), the languages switches back to the default language, after you have switched to another language (with parameter setlang=...)

• make sure that you have a favicon.ico on your site. Requesting favicon.ico MUST NOT return the GetSimple not-found page!

When editing pages you might have issues. There seems to be alot of XSS reflection false positives going on.

I get javascript halts if I simply enter an img
<img src="http://domain.com/test.png" />

Console will show
Refused to execute a JavaScript script. Source code of script found within request.

Still investigating.

EDIT:
Only happening in 3.1, i wonder ifs its the new js queueing with the version numbers.

http://groups.google.com/a/chromium.org … &pli=1

Supposedly you can send a header
X-XSS-Protection: 0
I guess ill try that only on edit pages.

For the next release of GetSimple 3.1 we are introducing Script and Style queuing on the system to allow Theme and Plugin writers to include your own Javascript and styles easily with your plugin distributions.

This will also give us a standard way of loading standard script such as JQuery, JQuery-UI, fancybox etc... and ensure that only one copy of each is loaded.

GetSimple 3.1 comes preconfigured with the following scripts and styles preconfigured ready for queuing on your pages.

Scripts

• jquery - CDN version of Jquery

• jquery-ui - CDN version of JQuery UI

• fancybox - Fancybox lighbox script

• getsimple - GetSimple site Javascript

Styles

• getsimple - Getsimple Site CSS

By default Jquery, Fancybox & Getsimple scripts and the Getsimpel Stylesheet are loaded on the back-end pages.

We recommend that if you are including your own scripts and styles that you store them in a seperate folder in your plugin folder, /my_plugin_folder/js for your javascript files /my_plugin_folder/css for your stylesheets

Scripts

To register your script with the system  use the following in your plugin.

register_script($handle, $src, $ver, $in_footer=FALSE)

Where
$handle = unique name for your script.
$src = src location of your script.
$ver = version of your script file
$in_footer = whether to load the script after the footer.

So for example to register a script from your plugin folder use:

register_script('myscript', $SITEURL.'plugins/myplugin/myscript.js', '0.1', FALSE);

To load the script for use on the back-end pages you need to queue it.

queue_script('myscript', GSBACK);  
// use GSFRONT to load a script with your theme, GSBOTH for theme and Admin

If your plugin requires say JQuery on the frontend just queue it

queue_script('myscript', GSFRONT);  

Styles

Styles are registered and queued in the same way as scripts.

register_style($handle, $src, $ver, $media)

Where
$handle = unique name for your style.
$src = src location of your style.
$ver = version of your file
$media  = Media type for CSS file

Then just queue your style for use with the system

queue_style('mystyle', GSBACK);  
// use GSFRONT to load a script with your theme, GSBOTH for theme and Admin

Themes

Theme writers should also register scripts/styles instead of hardcoding them into the theme as we can ensure that only one copy of the scripts are loaded.

Please let us know if you any suggestions or comments on the new system .

Mike...

Latest Stable Version: 2.5.3
http://get-simple.info/extend/plugin/gs … allery/85/

Google Code Project Page:
http://code.google.com/p/gsgallery/

ISSUES?
Please when posting a new issue here, make sure:

• You review previous posts by others, sometimes the solutions have been posted by other users

• The issue is not listed in the google code page http://code.google.com/p/gsgallery/issues/list/

• You put the version number of the plugin

• You put the version number of the Get Simple CMS

Feel free to create a new issue in the google code page, but it might be a good idea to also drop a message here and link it to the actual issue. Thanks.

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

*Be sure once you download the plugin file to read the change log to see what has changed.

I will be creating some sort of help document as soon I have some extra time. In the mean time, let me give you a quick reference:

To install:
- Unzip and upload the content of the plugin file into the "plugins" directory inside of GetSimple.
- Once uploaded make sure that you have the correct permissions. I would set all the contents inside the plugin to 755 or higher.

To use:
- Upload some images to get simple using the file uploader tab
- then go to the Image Gallery Tab and create a new gallery.
- select the images you want to display in the gallery and put the corresponding captions
- save the gallery and once in the list view, select the "CODE" and copy it.
- now go to the page you want to see the gallery and edit it (Pages Tab)
- paste the code you copied and save the page and you should be all set up.
- go the the front end and double check everything is working as expected

2.5 Beta Features (How To)

The new display function. 

squareit_gallery($gallery_id, $return);

With the new version of GSgallery 2.5 you will be able to use this display function to include galleries within your template, component, or if you are using the exec_php plugin.

Params: 

• $gallery_id => The ID of the gallery (without the squareit_gallery) so if the code is "squareit_gallery_4bdafa5d584f6" you only need "4bdafa5d584f6" 

• $return => Boolean (true/false) - This if set true, insead of the function echoing the output, it will return the output.

Firebug reports an error:
CKEDITOR.dialog.validate.inlineStyle is not a function
in <root>/admin/template/js/ckeditor/plugins/image/dialogs/image.js?t=B1GG4Z6 (line 13)

So I want to manage my site with Chrome, but here the "Browser Server"-Dialog does not work. Chrome opens a new window, but does not show it.

Only IE works fine ... I hate IE for that! ;)

Sorry I don't spend as much time here as I would like.

I have just had a look at v3.1B (r635) and I see that there is now a dependency on googleapis.com for jquery in the admin backend.

Is there any reason why this is loaded from Google, rather than from the website server? I understand the (theoretical) advantages of using Google to serve such libraries, but this is my problem:

I normally use NoScript on Firefox to disable javascript by source URL. This means that I can be selective about what scripts are running in my browser. (This is as much a speed/performance thing as a privacy concern.)

To use essential functionality in GS 3.1 admin, I now have to enable javascript from googleapis.com, which opens up a whole raft of other scripts and web functions that get in my way – translations, fonts, visual effects, for example – and that I really don't want to have.

I can provide my own local solution for this, but thought that a bit of feedback might be of interest. Is there a particular reason for using jQuery from this source?

Thanks.

I'm sure this is a stupid question, but I'll ask it anyway :

Are there special instructions for upgrading an installation of 3.0 (functional) to 3.1?

In the wiki it is not even mentioned this type of upgrade between these two versions.

First change is I renamed it to Simple Mobile Theme Changer because I have added support for
both Android, and webOS mobile browsers. (Untested but should work without a problem!)

I have added a few options in the settings page, mainly the ability to type in what the name of the appropriate theme is for the matching browser.

Please let me know if you see any issues!

To install just unzip and copy files to 'site/plugins/'

Installation

You can download the latest version from here. Unzip the downloaded file and copy its contents to your plugins folder. The required data folder and configuration file should be created automatically when you first access the plugin.

Usage

To access the plugin, go to the News Manager submenu under the Pages tab. Once you're in the News Manager main admin panel, you will notice  three buttons in the top-right corner: Settings,  Create New Post and Filter. The Settings button allows you to change the behavior of the News Manager plugin, with the Create New Post button you can start writing new posts and the Filter button lets you search through long lists of posts.

Settings

The settings panel currently has 7 different options, each of which will be explained in more detail in the list below.

• Page To Display Posts - Select the slug (url) of the page on which you want to display your posts. The original content of this page will be replaced with the posts that you have published.

• Language used on News Page - This controls the language settings for things like 'Published on', 'Older/Newer Posts', etc on the news page. Note that it won't affect the settings for the admin section of the News Manager plugin, that follows the global setting.

• Posts On News Page Are Shown As - You can choose for either Full Text or Excerpt. The first option will show each post as is, the second option displays an automatically created excerpt without html formatting for each post.

• Excerpt Length - This number defines the length in characters of the automatically created excerpts.

• Number Of Posts On News Page - This controls pagination. Whenever the total number of published posts exceeds the number entered here, a navigation menu will be shown at the bottom of the news page, allowing the user to navigate between pages with posts.

• Number Of Recent Posts - This plugin comes with a few (optional) sidebar functions, one of which provides a list with titles of the most recent posts. The value entered here controls how many titles are shown at each time.

• Use Fancy URLs for posts, archives, etc - If you enabled fancy URLs in the global GetSimple settings, you can enable them for the News Manager plugin too. When activated, you will have to update your .htaccess file because otherwise it will not work! If applicable, after you have saved your settings a notification will appear with a link to a page explaining you how to change your .htaccess file.

Writing Posts

Writing posts is more or less similar to writing pages: you can define a Post Title, and write the Post Content just as regular pages. Clicking on the Post Options button in the top-right corner reveals some extra options which are Slug/URL, Tags, Publication date and the ability to make a post Private. A page slug is a user- and SEO-friendly short text used in the post URL. In the Tags field you can enter whatever keywords you see fit, as long as they are single words and seperated by commas. The publication date speaks for itself and making a post private prevents it from being displayed on the front-end part of your website.

Sidebar Functions

A couple of optional sidebar functions are also availabe. They can be found in the file sidebar.php which is located in the /plugins/news_manager/inc/ folder. What follows is a short description of what each function does:

• nm_list_recent - Shows a list with the titles of the most recent articles, each title links to the full article.

• nm_list_archives - Creates a list with archives. Archives are ordered by month and each archive contains all posts that have been published in that specific month.

• nm_list_tags - Shows all unique tags in a tag cloud. Frequently used tags are shown bigger than others.

• nm_search - Provide a form to search articles based on keywords.

For example,  to show a list of recently published articles in the sidebar, simply put the following code in you theme template:

<?php nm_list_recent(); ?>

Languages

There are multiple language files included, they can be found in the /plugins/news_manager/lang/ folder. You can create your own language file by translating any of the existing ones. Please contact me (via the GS forum topic or PM) when you have created a new language file and I will include it in the next release.

CSS

This plugin uses various CSS classes (title, date, content, etc), but you have to write your own CSS rules in order to apply a style of your liking. CSS code for the GetSimple Innovation theme is shown below.

.nm_post {
  padding: 0;
  margin-bottom: 50px;
}

.nm_post h3 {
  margin-bottom: 5px;
}

.nm_post p {
  margin-bottom: 10px;
}

.nm_post_title a {
  text-decoration: none;
}

.nm_post_title a:hover {
  text-decoration: underline;
}

.nm_post_date {
  color: #999;
  font-size: 11px;
}

.nm_post_content {
  margin-bottom: 20px;
}

.nm_post_meta {
  padding: 2px 5px;
  border: 1px solid #ccc;
  background-color: #f9f9f9;
  font-size: 11px;
}

.nm_post_back {
  margin-top: 20px;
  font-size: 11px;
}

.nm_post_back a {
  text-decoration: none;
}

.nm_post_back a:hover {
  text-decoration: underline;
}

.nm_page_nav .left {
  float:left;
  text-align:left;
}

.nm_page_nav .right {
  float:right;
  text-align:right;
}

aside .section a, aside .section a {
  text-decoration: none;
}

aside .section a:hover, aside .section a:hover {
  text-decoration: underline;
}

aside .section a.large {
  font-size: 22px;
}

That's it, I hope you will enjoy it!

A simple plugin, but it is useful.

Please report me about bugs and ideas.

http://get-simple.info/extend/plugin/so … ons-3/201/

example on http://diretto.biz