3.4.0 wish list

[dstasinski]

Relative URL's in everything.

Without relative URL's, it's virtually impossible to allow for both 'http' and 'https' connections. Every link breaks the visitor out of SSL, themes fail, images do not load, etc. It's pretty messy.

[shawn_a]

already done, i actually reread this entire thread and most of it is already done in 3.4, albeit untested and raw.

I actually will need alot of testers to test master branch for this soon. ( its live now as default in master branch on github actually if your brave )

oh and protocolless assets in backend is in 3.3.3 already i think.

[mganko]

already done, i actually reread this entire thread and most of it is already done in 3.4, albeit untested and raw.

I actually will need alot of testers to test master branch for this soon. ( its live now as default in master branch on github actually if your brave )

oh and protocolless assets in backend is in 3.3.3 already i think.

I've downloaded 3.4 from github and menu manager is still not multilevel?
Multilevel menu will be implemented or not?

Where to post 3.4 issues? Can I on Github?

[shawn_a]

Ill make a thread soon, its still in development, not alpha yet

I was referring to testing relative urls.

[mganko]

I would like to have in 3.4 better universal css styles to use in plugins etc.:

• styles for small buttons. Now there is a style declaration for .edit-nav a but it's not usable because of it's .edit-nav parent container. Also dark color in my opinion is not good for buttons across page functionality
  
• style for textarea. Text and select input are now styled but textarea not.
  
• unify look of 'page options' inputs, now they're have smaller padding than inputs because there is a #metadata_window style declaration
  

[shawn_a]

Some of this has already been addressed, textareas should be in .wideopt containers I think, which wasmade available several versions ago.

Check out master branch and see what else is needed specifically and ill add it.
Some things like edit nav buttons are like that so they are not used elsewhere in the UI, they are very distinct and only are used in that location, i think reusing or promoting that style elsewhere would clutter the UI.

#metadata_window no longer exists, page options are tabbed now

[mganko]

Some of this has already been addressed, textareas should be in .wideopt containers I think, which wasmade available several versions ago.

Check out master branch and see what else is needed specifically and ill add it.
Some things like edit nav buttons are like that so they are not used elsewhere in the UI, they are very distinct and only are used in that location, i think reusing or promoting that style elsewhere would clutter the UI.

#metadata_window no longer exists, page options are tabbed now

What are you thinking about these changes:

• use box-sizing: border-box;. It's easier to control width of inputs, etc.
  
• .wideopt - remove max-width: 600px; to fill empty space
  
• .leftopt, .rightopt remove max-widh: 300px; and set width to 50%. Also adding little space between that columns will look better in Options and Meta tab.
  
• upgrading jQuery and jQuery UI
  

So would bo nice to have GS button styles (small, medium, big) than plugins UI will look similiar.

Where are fancybox js plugin used?

[shawn_a]

You should really read the 3.4 milestone issues on github or check the code first, I am fairly certain i have changed all these things.

[shawn_a]

I will take suggestions for button sizes, with specific use cases.
screenshots would be nice

[mganko]

You should really read the 3.4 milestone issues on github or check the code first, I am fairly certain i have changed all these things.

Shawn, none of this css modifications can be found in 3.4 dowloaded just few days ago.

Here's screenshot of button usage:

[shawn_a]

inputs are set to content-box, I don't remember why. I changed to border-box

also
.wideopt {
max-width:600px;
}

.leftopt,.rightopt {
max-width:300px;
}

exist because the wrapper is now larger and adjustable, and i have not figured out what do with fields when you have it at 100% or something like 1600, this is in style wide which is still in development.

set

PHP Code:

define('GSWIDTH','0'); // css value px, %  0 or '' will be treated as 100% 


and see the problem, and I probably wont have the resources to add media queries, or be able to support plugins decently with them. Ideas welcome.

I could always set min-width and float:left on the .*opts and let them stack horizontally, it doesn't look to bad.

[shawn_a]

changes for option groups responsiveness and consistency.
https://github.com/GetSimpleCMS/GetSimpleCMS/issues/934

[phpman]

Hi Shawn,

is it possible to implement the possibility to show/delete errorlog (not only failedlogins.log) in the backend of GS ?

br,
Harald

[shawn_a]

I thought about this, it will not be added in core, but 3.4 has all the hooks in place to allow a plugin to do it.

I think someone created a plugin for this already, but it might not be in extend, i cant find it.

[cumbe]

Hi phpman,
you can see it in: http://get-simple.info/forums/showthread.php?tid=5791

It's a plugin that I did, but like it was not very successful I didn't upload to extend.

Regards

Hi Shawn,

is it possible to implement the possibility to show/delete errorlog (not only failedlogins.log) in the backend of GS ?

br,
Harald

[shawn_a]

Yeah I was thinking of that plugin, I was mistaken it seems.
That plugin does much more than just show the error log.

[mganko]

changes for option groups responsiveness and consistency.
https://github.com/GetSimpleCMS/GetSimpleCMS/issues/934

Thanks for changes. What about button styles that can be used across plugins?

[shawn_a]

I was originally against it, but your screenshot helps make your argument, thanks. Will think about it.
The problem with button sizes, is can can only control style and font-size, length needs to be variable for i18n.

I have added labels to 3.4, which could be used for buttons, but might be confusing, and i have not finalized it yet for that reason.

[mganko]

I was originally against it, but your screenshot helps make your argument, thanks. Will think about it.
The problem with button sizes, is can can only control style and font-size, length needs to be variable for i18n.

I have added labels to 3.4, which could be used for buttons, but might be confusing, and i have not finalized it yet for that reason.

I think styling font size to make buttons different sizes will be enough.
Tak a look here in SIZES section: http://getbootstrap.com/css/#buttons something similiar would be great.
Of course we need styles for disabled, enchanced states of buttons too.

[DimaYakovlev]

Switching to Bootstrap or other framework will make creating interface for new plugins easier.

[mganko]

Switching to Bootstrap or other framework will make creating interface for new plugins easier.

Having Bootstrap admin theme, with modern look would be perfect. Shawn is it possible in future?

[shawn_a]

Maybe, it would sure as hell make my job easier. But I am hesitant to use a framework that will become outdated quickly and require maintenance. I would rather use a templating system that can have a framework plugged in to it, so it can be switched out.

[buitje68]

Today i found a website with a nice aproach for putting a complete site in maintenance mode by using the .htaccess file.

http://perishablepress.com/htaccess-redi...e-updates/

# MAINTENANCE-PAGE REDIRECT
<IfModule mod_rewrite.c>
RewriteEngine on
RewriteCond %{REMOTE_ADDR} !^123\.456\.789\.000
RewriteCond %{REQUEST_URI} !/maintenance.html$ [NC]
RewriteCond %{REQUEST_URI} !\.(jpe?g?|png|gif) [NC]
RewriteRule .* /maintenance.html [R=302,L]
</IfModule>

It would be nice, if this could be added in the admin panel.

Options i suggest:
- Custom page/template for maintenance / local html file
- Interface for addind the 'bypass/admin' ip's

my 2 cents...

[shawn_a]

I use this personally for some sites, but ideally this method of maint is a pain, its a protected file, not all host allow this, only works o apache, have to edit a file every time,

however something like this is the only way to ACTUALLY put a site into maint mode as it blocks all requests.

[superyms]

Hi,

I have discovered 5 years ago GetSimple. 3 days ago, i was looking for an easy solution to make a website without a need for any database and than i reminded it ! GetSimple (it grows nicely !!).

what would be nice for GS 3.4.0 (actually testing 3.3.5) is :

- dispose of its own css-framework for GS (with usability for back-admin- and front-public- end), so the maintenance would be easy ?!

- in the "link button" in ckeditor, as you have made easy to make links to local pages, it would be very nice to have links to local documents (images, pdf, ...)

- in the files section it would be nice to have:
* possibility (like on the listing used when you incorporated an image in the editor) to have a small icon of the image,
* possibility to have a button to generate thumbs (yes sometimes i upload images directly by ftp, so the system does not generate thumbnails)

- on the page management, beside view or delete page the possibility to :
* change its state to private directly from there,
* possibility to duplicate/clone a page from there,
* ability to archive a page (another state)
* also having to filter by date pages

- in the page options (edit page) : ability to have access to publication date (a "wrote date" could be fix and not accessible, the date that really the page started its existence) that we could change if needed.

- in plugins management, it would be more easier and logic to see the description of the plugin even if this one is disabled...actually i have to activate a plugin just to read the description...it could stay grey colored background to indicate the inactive mode.

- include a humans.txt file (like robots.text one), here to check about it :http://humanstxt.org/

- having a plugin or a section dedicated to statistics, nothing really very advanced but with a nice visuals o number of visits, monitoring visits (side "Site"), the number of unique visitors (1 unique visitor ip = 1), the number of pages requested, viewing the Administration side statistics (with pretty graphs based on Chart.js, or another solution) and ability to choose the number of days stored in the statistic configuration screen (after 2 days of storage, the same plugin offers information tracking weight of the storage file in this screen) and without any display on site
I know that google analytics exists and other solutions, but sometimes it would be fun to have a sight by yourself...

In my view this is my first proposals for the next version of GS.
I hope you will continue to propose such a wonderful tool, yes it is really simple to use ! thank you for the core team and all contributors, testers and users.

i wonder if i could help somehow ? let me know.