CMS Made Simple Forums

htmlblobs (aka global content blocks) are NOT design, they are NOT layout. they are CONTENT (hence the name "global CONTENT blocks"). so why the heck are they removed and converted into design elements (templates). not only can you no longer just pop-in to add some blobs then insert them; ...

Multiple CSVs, up to and over 45 megabytes each, that you want to be able to modify via a web interface..... no question, definitely need a database for best performance. There are a few "module maker" type modules. Try 'em out on a test setup (e.g. XAMPP or similar) and see which one work...

Yup, IDs cannot start with a number... they should also be unique on a page. So, you need to use classes instead of IDs or use two "prefixes", one for the UL submenus, the other for the actual menu items.. example below, based on minimal_menu.tpl, uses the latter. {* entire menu is <ul id=...

One of CMS Made Simple's strengths is how easy it is to create page templates for it, based on designs you have cooked-up in whatever application or editor you choose, whether it be a plain text editor like vi or Notepad++ or a WYSIWYG application like Dreamweaver. Smarty is an integral part of CMS ...

jpatti wrote: That's ridiculous that you can "educate" customers like that.

it's easy.. especially when it's the only way you've ever done things... 

I would like to take a sec as there seems to be some confusion as to why minify (thou you can turn it off in ScriptDeploy) gzip a stylesheet vs minified then gzip..  the differences in output size is minimal.  I truly wish that was true. but if you will not take the big 3's word for it.. a little p...

does the content in the csv contain actual pages or just data to use within a page (e.g. with a udt that reads the csv and outputs the data to display)? how much data is there (e.g. number of csv fields, how many rows?) will the csv data change? if so, how do you want to modify that data (e.g. insid...

Based on the above upgrade path I might as well start from scratch for the older websites, it will take less time and a better resulting product. But why would someone pay for a redesign of a website to look the same as the old one just because there is a newer version of the software? if you're on...

Thanks for the comments. I tried your suggestion kermit, and with a bit of trial and error about where to put the rewrite statement relative to the exisitng ones, got a solution. It only worked if I kept the redirects in too - wierd! shouldn't need those. i put rewriterule-based page redirects for ...

i was looking at doing the same thing, using per-page extra attribute for meta tags such as 'description', but the field length (255) is too short for some implementations.

use the {page_attr} tag to get the extra attributes into smarty variables: in your page content... {page_attr key='extra1' assign='myvar1'} then {$myvar1} would contain extra1 if you need more than three, use the page-specific smarty logic ('options' tab when editing page) and simply assign variable...

There is however a trade off. Because the style sheets are stored in the tmp/cache directory, the relative directory of the style sheets is not the same, users should use the [[root_url]] smarty tag in their style sheets to force absolute references to images that are specified in style sheets. mig...

sorry, i don't use the simplepie module, but you can {$thearray|print_r} the array(s) it uses to see if what you're looking for is in it... i do use the RSS2HTML module, though, and i can tell you that the data you want to use is readily available: inside the main template loop {foreach from=$rss->i...

it could be done.. but would take some work... need to be able to set nms to send only xx number of mails when a job is run, then automatically pause it.  log and/or send to admin the results of these automated 'batches' instead of presenting on screen... needs some sort of "cron" support....

try using mod_rewrite's rewriterule instead... e.g. # redirects for obsolete urls RewriteRule ^services/$ /our-super-duper-keyword-stuffed-annoyingly-long-url-for-our-services-page/ [NC,L,R=301] RewriteRule ^services\.html$ /our-super-duper-keyword-stuffed-annoyingly-long-url-for-our-services-page/ ...