browsercms 3.0.0 → 3.0.1

Sign up to get free protection for your applications and to get access to all the features.
Files changed (444) hide show
  1. data/app/controllers/cms/connectors_controller.rb +1 -1
  2. data/app/helpers/cms/application_helper.rb +2 -19
  3. data/app/helpers/cms/form_builder.rb +8 -5
  4. data/app/helpers/cms/menu_helper.rb +19 -5
  5. data/app/helpers/cms/page_helper.rb +9 -1
  6. data/app/helpers/cms/template_support.rb +21 -0
  7. data/app/models/abstract_file_block.rb +4 -0
  8. data/app/models/connector.rb +7 -3
  9. data/app/models/dynamic_view.rb +2 -4
  10. data/app/models/portlet.rb +22 -9
  11. data/app/models/section.rb +7 -5
  12. data/app/views/cms/blocks/_toolbar_for_member.html.erb +4 -4
  13. data/app/views/cms/blocks/index.html.erb +1 -1
  14. data/app/views/cms/blocks/usages.html.erb +44 -34
  15. data/app/views/cms/connectors/new.html.erb +2 -2
  16. data/app/views/cms/dynamic_views/_form.html.erb +1 -1
  17. data/app/views/cms/dynamic_views/index.html.erb +7 -3
  18. data/app/views/cms/email_messages/index.html.erb +3 -5
  19. data/app/views/cms/form_builder/_cms_datetime_select.html.erb +12 -0
  20. data/app/views/cms/form_builder/_cms_text_editor.html.erb +2 -2
  21. data/app/views/cms/form_builder/_cms_text_field.html.erb +1 -2
  22. data/app/views/cms/groups/_permissions.html.erb +1 -0
  23. data/app/views/cms/groups/_sections.html.erb +1 -0
  24. data/app/views/cms/groups/index.html.erb +3 -5
  25. data/app/views/cms/page_routes/index.html.erb +13 -7
  26. data/app/views/cms/page_routes/show.html.erb +4 -4
  27. data/app/views/cms/pages/_edit_connector.html.erb +4 -1
  28. data/app/views/cms/pages/_edit_container.html.erb +4 -1
  29. data/app/views/cms/redirects/index.html.erb +12 -7
  30. data/app/views/cms/routes/index.html.erb +11 -7
  31. data/app/views/cms/sections/_form.html.erb +4 -5
  32. data/app/views/cms/users/_groups.html.erb +1 -0
  33. data/app/views/layouts/_cms_toolbar.html.erb +37 -4
  34. data/app/views/layouts/_page_toolbar.html.erb +2 -2
  35. data/browsercms.gemspec +381 -3
  36. data/db/demo/data.rb +2 -1
  37. data/doc/app/classes/AbstractFileBlock.html +146 -0
  38. data/doc/app/classes/ActiveRecord.html +105 -0
  39. data/doc/app/classes/ActiveRecord/ConnectionAdapters/SchemaStatements.html +242 -0
  40. data/doc/app/classes/ActiveSupport.html +111 -0
  41. data/doc/app/classes/ActiveSupport/Cache.html +111 -0
  42. data/doc/app/classes/ActiveSupport/Cache/FileStore.html +146 -0
  43. data/doc/app/classes/ActsAsList.html +147 -0
  44. data/doc/app/classes/ActsAsList/ClassMethods.html +202 -0
  45. data/doc/app/classes/ActsAsList/InstanceMethods.html +510 -0
  46. data/doc/app/classes/ApplicationController.html +119 -0
  47. data/doc/app/classes/ApplicationHelper.html +112 -0
  48. data/doc/app/classes/Attachment.html +726 -0
  49. data/doc/app/classes/Category.html +230 -0
  50. data/doc/app/classes/CategoryType.html +214 -0
  51. data/doc/app/classes/Cms.html +638 -0
  52. data/doc/app/classes/Cms/Acts.html +111 -0
  53. data/doc/app/classes/Cms/Acts/ContentBlock.html +146 -0
  54. data/doc/app/classes/Cms/Acts/ContentBlock/MacroMethods.html +165 -0
  55. data/doc/app/classes/Cms/Acts/ContentBlock/MacroMethods/InstanceMethods.html +140 -0
  56. data/doc/app/classes/Cms/ApplicationController.html +418 -0
  57. data/doc/app/classes/Cms/ApplicationHelper.html +814 -0
  58. data/doc/app/classes/Cms/AttachmentsController.html +154 -0
  59. data/doc/app/classes/Cms/Authentication.html +116 -0
  60. data/doc/app/classes/Cms/Authentication/Controller.html +702 -0
  61. data/doc/app/classes/Cms/Authentication/Model.html +165 -0
  62. data/doc/app/classes/Cms/Authentication/Model/ClassMethods.html +246 -0
  63. data/doc/app/classes/Cms/Authentication/Model/InstanceMethods.html +412 -0
  64. data/doc/app/classes/Cms/BaseController.html +113 -0
  65. data/doc/app/classes/Cms/Behaviors.html +235 -0
  66. data/doc/app/classes/Cms/Behaviors/Archiving.html +147 -0
  67. data/doc/app/classes/Cms/Behaviors/Archiving/InstanceMethods.html +220 -0
  68. data/doc/app/classes/Cms/Behaviors/Archiving/MacroMethods.html +175 -0
  69. data/doc/app/classes/Cms/Behaviors/Attaching.html +160 -0
  70. data/doc/app/classes/Cms/Behaviors/Attaching/InstanceMethods.html +670 -0
  71. data/doc/app/classes/Cms/Behaviors/Attaching/MacroMethods.html +188 -0
  72. data/doc/app/classes/Cms/Behaviors/Categorizing.html +148 -0
  73. data/doc/app/classes/Cms/Behaviors/Categorizing/ClassMethods.html +105 -0
  74. data/doc/app/classes/Cms/Behaviors/Categorizing/InstanceMethods.html +140 -0
  75. data/doc/app/classes/Cms/Behaviors/Categorizing/MacroMethods.html +178 -0
  76. data/doc/app/classes/Cms/Behaviors/ClassMethods.html +272 -0
  77. data/doc/app/classes/Cms/Behaviors/Connecting.html +148 -0
  78. data/doc/app/classes/Cms/Behaviors/Connecting/ClassMethods.html +188 -0
  79. data/doc/app/classes/Cms/Behaviors/Connecting/InstanceMethods.html +312 -0
  80. data/doc/app/classes/Cms/Behaviors/Connecting/MacroMethods.html +184 -0
  81. data/doc/app/classes/Cms/Behaviors/DynamicAttributes.html +285 -0
  82. data/doc/app/classes/Cms/Behaviors/DynamicAttributes/InstanceMethods.html +181 -0
  83. data/doc/app/classes/Cms/Behaviors/DynamicAttributes/MacroMethods.html +243 -0
  84. data/doc/app/classes/Cms/Behaviors/FlushCacheOnChange.html +178 -0
  85. data/doc/app/classes/Cms/Behaviors/FlushCacheOnChange/InstanceMethods.html +142 -0
  86. data/doc/app/classes/Cms/Behaviors/FlushCacheOnChange/MacroMethods.html +175 -0
  87. data/doc/app/classes/Cms/Behaviors/Hiding.html +148 -0
  88. data/doc/app/classes/Cms/Behaviors/Hiding/ClassMethods.html +105 -0
  89. data/doc/app/classes/Cms/Behaviors/Hiding/InstanceMethods.html +220 -0
  90. data/doc/app/classes/Cms/Behaviors/Hiding/MacroMethods.html +176 -0
  91. data/doc/app/classes/Cms/Behaviors/InstanceMethods.html +234 -0
  92. data/doc/app/classes/Cms/Behaviors/Pagination.html +151 -0
  93. data/doc/app/classes/Cms/Behaviors/Pagination/ClassMethods.html +252 -0
  94. data/doc/app/classes/Cms/Behaviors/Pagination/Collection.html +437 -0
  95. data/doc/app/classes/Cms/Behaviors/Pagination/InvalidPage.html +146 -0
  96. data/doc/app/classes/Cms/Behaviors/Publishing.html +179 -0
  97. data/doc/app/classes/Cms/Behaviors/Publishing/ClassMethods.html +105 -0
  98. data/doc/app/classes/Cms/Behaviors/Publishing/InstanceMethods.html +333 -0
  99. data/doc/app/classes/Cms/Behaviors/Publishing/MacroMethods.html +180 -0
  100. data/doc/app/classes/Cms/Behaviors/Rendering.html +179 -0
  101. data/doc/app/classes/Cms/Behaviors/Rendering/MacroMethods.html +186 -0
  102. data/doc/app/classes/Cms/Behaviors/Searching.html +147 -0
  103. data/doc/app/classes/Cms/Behaviors/Searching/ClassMethods.html +164 -0
  104. data/doc/app/classes/Cms/Behaviors/Searching/MacroMethods.html +188 -0
  105. data/doc/app/classes/Cms/Behaviors/SoftDeleting.html +148 -0
  106. data/doc/app/classes/Cms/Behaviors/SoftDeleting/ClassMethods.html +217 -0
  107. data/doc/app/classes/Cms/Behaviors/SoftDeleting/InstanceMethods.html +247 -0
  108. data/doc/app/classes/Cms/Behaviors/SoftDeleting/MacroMethods.html +205 -0
  109. data/doc/app/classes/Cms/Behaviors/Taggable.html +148 -0
  110. data/doc/app/classes/Cms/Behaviors/Taggable/ClassMethods.html +164 -0
  111. data/doc/app/classes/Cms/Behaviors/Taggable/InstanceMethods.html +197 -0
  112. data/doc/app/classes/Cms/Behaviors/Taggable/MacroMethods.html +182 -0
  113. data/doc/app/classes/Cms/Behaviors/Userstamping.html +148 -0
  114. data/doc/app/classes/Cms/Behaviors/Userstamping/ClassMethods.html +105 -0
  115. data/doc/app/classes/Cms/Behaviors/Userstamping/InstanceMethods.html +143 -0
  116. data/doc/app/classes/Cms/Behaviors/Userstamping/MacroMethods.html +181 -0
  117. data/doc/app/classes/Cms/Behaviors/Versioning.html +148 -0
  118. data/doc/app/classes/Cms/Behaviors/Versioning/ClassMethods.html +237 -0
  119. data/doc/app/classes/Cms/Behaviors/Versioning/InstanceMethods.html +685 -0
  120. data/doc/app/classes/Cms/Behaviors/Versioning/MacroMethods.html +290 -0
  121. data/doc/app/classes/Cms/CacheController.html +174 -0
  122. data/doc/app/classes/Cms/Caching.html +171 -0
  123. data/doc/app/classes/Cms/CategoriesController.html +113 -0
  124. data/doc/app/classes/Cms/CategoryTypesController.html +148 -0
  125. data/doc/app/classes/Cms/ConnectorsController.html +215 -0
  126. data/doc/app/classes/Cms/ContentBlockController.html +1175 -0
  127. data/doc/app/classes/Cms/ContentController.html +313 -0
  128. data/doc/app/classes/Cms/ContentTypesController.html +148 -0
  129. data/doc/app/classes/Cms/DashboardController.html +151 -0
  130. data/doc/app/classes/Cms/DataLoader.html +182 -0
  131. data/doc/app/classes/Cms/DynamicViewsController.html +359 -0
  132. data/doc/app/classes/Cms/EmailMessagesController.html +172 -0
  133. data/doc/app/classes/Cms/ErrorHandling.html +172 -0
  134. data/doc/app/classes/Cms/Errors.html +111 -0
  135. data/doc/app/classes/Cms/Errors/AccessDenied.html +146 -0
  136. data/doc/app/classes/Cms/Extensions.html +140 -0
  137. data/doc/app/classes/Cms/Extensions/ActionView.html +111 -0
  138. data/doc/app/classes/Cms/Extensions/ActionView/Base.html +141 -0
  139. data/doc/app/classes/Cms/Extensions/ActiveRecord.html +116 -0
  140. data/doc/app/classes/Cms/Extensions/ActiveRecord/Base.html +144 -0
  141. data/doc/app/classes/Cms/Extensions/ActiveRecord/Errors.html +140 -0
  142. data/doc/app/classes/Cms/Extensions/Hash.html +175 -0
  143. data/doc/app/classes/Cms/Extensions/Integer.html +146 -0
  144. data/doc/app/classes/Cms/Extensions/NilClass.html +212 -0
  145. data/doc/app/classes/Cms/Extensions/String.html +212 -0
  146. data/doc/app/classes/Cms/FileBlocksController.html +113 -0
  147. data/doc/app/classes/Cms/FormBuilder.html +312 -0
  148. data/doc/app/classes/Cms/FormTagHelper.html +245 -0
  149. data/doc/app/classes/Cms/GroupsController.html +225 -0
  150. data/doc/app/classes/Cms/HomeController.html +148 -0
  151. data/doc/app/classes/Cms/HtmlBlocksController.html +113 -0
  152. data/doc/app/classes/Cms/ImageBlocksController.html +113 -0
  153. data/doc/app/classes/Cms/LinksController.html +341 -0
  154. data/doc/app/classes/Cms/MenuHelper.html +330 -0
  155. data/doc/app/classes/Cms/PageHelper.html +292 -0
  156. data/doc/app/classes/Cms/PageRouteConditionsController.html +113 -0
  157. data/doc/app/classes/Cms/PageRouteOptionsController.html +355 -0
  158. data/doc/app/classes/Cms/PageRouteRequirementsController.html +113 -0
  159. data/doc/app/classes/Cms/PageRoutesController.html +284 -0
  160. data/doc/app/classes/Cms/PagesController.html +331 -0
  161. data/doc/app/classes/Cms/PathHelper.html +268 -0
  162. data/doc/app/classes/Cms/PortletController.html +150 -0
  163. data/doc/app/classes/Cms/PortletsController.html +301 -0
  164. data/doc/app/classes/Cms/RedirectsController.html +172 -0
  165. data/doc/app/classes/Cms/ResourceController.html +616 -0
  166. data/doc/app/classes/Cms/Routes.html +303 -0
  167. data/doc/app/classes/Cms/RoutesController.html +164 -0
  168. data/doc/app/classes/Cms/SectionNodesController.html +272 -0
  169. data/doc/app/classes/Cms/SectionNodesHelper.html +145 -0
  170. data/doc/app/classes/Cms/SectionsController.html +542 -0
  171. data/doc/app/classes/Cms/SessionsController.html +270 -0
  172. data/doc/app/classes/Cms/TagsController.html +152 -0
  173. data/doc/app/classes/Cms/TasksController.html +221 -0
  174. data/doc/app/classes/Cms/ToolbarController.html +153 -0
  175. data/doc/app/classes/Cms/UsersController.html +405 -0
  176. data/doc/app/classes/Connector.html +350 -0
  177. data/doc/app/classes/ContentType.html +448 -0
  178. data/doc/app/classes/ContentTypeGroup.html +111 -0
  179. data/doc/app/classes/DynamicPortlet.html +148 -0
  180. data/doc/app/classes/DynamicView.html +411 -0
  181. data/doc/app/classes/EmailMessage.html +228 -0
  182. data/doc/app/classes/EmailMessageMailer.html +150 -0
  183. data/doc/app/classes/EmailPagePortlet.html +184 -0
  184. data/doc/app/classes/FileBlock.html +202 -0
  185. data/doc/app/classes/Group.html +170 -0
  186. data/doc/app/classes/GroupPermission.html +111 -0
  187. data/doc/app/classes/GroupSection.html +111 -0
  188. data/doc/app/classes/GroupType.html +111 -0
  189. data/doc/app/classes/GroupTypePermission.html +111 -0
  190. data/doc/app/classes/GuestUser.html +347 -0
  191. data/doc/app/classes/HtmlBlock.html +170 -0
  192. data/doc/app/classes/ImageBlock.html +202 -0
  193. data/doc/app/classes/InitialData.html +171 -0
  194. data/doc/app/classes/Link.html +249 -0
  195. data/doc/app/classes/LoginPortlet.html +151 -0
  196. data/doc/app/classes/Page.html +954 -0
  197. data/doc/app/classes/PagePartial.html +201 -0
  198. data/doc/app/classes/PageRoute.html +335 -0
  199. data/doc/app/classes/PageRouteCondition.html +113 -0
  200. data/doc/app/classes/PageRouteOption.html +111 -0
  201. data/doc/app/classes/PageRouteRequirement.html +113 -0
  202. data/doc/app/classes/PageTemplate.html +278 -0
  203. data/doc/app/classes/Permission.html +111 -0
  204. data/doc/app/classes/Portlet.html +738 -0
  205. data/doc/app/classes/Redirect.html +111 -0
  206. data/doc/app/classes/Section.html +580 -0
  207. data/doc/app/classes/SectionNode.html +410 -0
  208. data/doc/app/classes/Sequence.html +146 -0
  209. data/doc/app/classes/Site.html +253 -0
  210. data/doc/app/classes/Tag.html +292 -0
  211. data/doc/app/classes/TagCloudPortlet.html +176 -0
  212. data/doc/app/classes/Tagging.html +146 -0
  213. data/doc/app/classes/Task.html +288 -0
  214. data/doc/app/classes/User.html +618 -0
  215. data/doc/app/classes/UserGroupMembership.html +111 -0
  216. data/doc/app/created.rid +1 -0
  217. data/doc/app/files/app/controllers/application_controller_rb.html +109 -0
  218. data/doc/app/files/app/controllers/cms/application_controller_rb.html +101 -0
  219. data/doc/app/files/app/controllers/cms/attachments_controller_rb.html +101 -0
  220. data/doc/app/files/app/controllers/cms/base_controller_rb.html +101 -0
  221. data/doc/app/files/app/controllers/cms/cache_controller_rb.html +101 -0
  222. data/doc/app/files/app/controllers/cms/categories_controller_rb.html +101 -0
  223. data/doc/app/files/app/controllers/cms/category_types_controller_rb.html +101 -0
  224. data/doc/app/files/app/controllers/cms/connectors_controller_rb.html +101 -0
  225. data/doc/app/files/app/controllers/cms/content_block_controller_rb.html +107 -0
  226. data/doc/app/files/app/controllers/cms/content_controller_rb.html +101 -0
  227. data/doc/app/files/app/controllers/cms/content_types_controller_rb.html +101 -0
  228. data/doc/app/files/app/controllers/cms/dashboard_controller_rb.html +101 -0
  229. data/doc/app/files/app/controllers/cms/dynamic_views_controller_rb.html +101 -0
  230. data/doc/app/files/app/controllers/cms/email_messages_controller_rb.html +101 -0
  231. data/doc/app/files/app/controllers/cms/error_handling_rb.html +101 -0
  232. data/doc/app/files/app/controllers/cms/file_blocks_controller_rb.html +101 -0
  233. data/doc/app/files/app/controllers/cms/groups_controller_rb.html +101 -0
  234. data/doc/app/files/app/controllers/cms/home_controller_rb.html +101 -0
  235. data/doc/app/files/app/controllers/cms/html_blocks_controller_rb.html +101 -0
  236. data/doc/app/files/app/controllers/cms/image_blocks_controller_rb.html +101 -0
  237. data/doc/app/files/app/controllers/cms/links_controller_rb.html +101 -0
  238. data/doc/app/files/app/controllers/cms/page_route_conditions_controller_rb.html +101 -0
  239. data/doc/app/files/app/controllers/cms/page_route_options_controller_rb.html +101 -0
  240. data/doc/app/files/app/controllers/cms/page_route_requirements_controller_rb.html +101 -0
  241. data/doc/app/files/app/controllers/cms/page_routes_controller_rb.html +101 -0
  242. data/doc/app/files/app/controllers/cms/pages_controller_rb.html +101 -0
  243. data/doc/app/files/app/controllers/cms/portlet_controller_rb.html +101 -0
  244. data/doc/app/files/app/controllers/cms/portlets_controller_rb.html +101 -0
  245. data/doc/app/files/app/controllers/cms/redirects_controller_rb.html +101 -0
  246. data/doc/app/files/app/controllers/cms/resource_controller_rb.html +108 -0
  247. data/doc/app/files/app/controllers/cms/routes_controller_rb.html +101 -0
  248. data/doc/app/files/app/controllers/cms/section_nodes_controller_rb.html +101 -0
  249. data/doc/app/files/app/controllers/cms/sections_controller_rb.html +101 -0
  250. data/doc/app/files/app/controllers/cms/sessions_controller_rb.html +107 -0
  251. data/doc/app/files/app/controllers/cms/tags_controller_rb.html +101 -0
  252. data/doc/app/files/app/controllers/cms/tasks_controller_rb.html +101 -0
  253. data/doc/app/files/app/controllers/cms/toolbar_controller_rb.html +101 -0
  254. data/doc/app/files/app/controllers/cms/users_controller_rb.html +101 -0
  255. data/doc/app/files/app/helpers/application_helper_rb.html +108 -0
  256. data/doc/app/files/app/helpers/cms/application_helper_rb.html +107 -0
  257. data/doc/app/files/app/helpers/cms/form_builder_rb.html +101 -0
  258. data/doc/app/files/app/helpers/cms/form_tag_helper_rb.html +101 -0
  259. data/doc/app/files/app/helpers/cms/menu_helper_rb.html +101 -0
  260. data/doc/app/files/app/helpers/cms/page_helper_rb.html +101 -0
  261. data/doc/app/files/app/helpers/cms/path_helper_rb.html +101 -0
  262. data/doc/app/files/app/helpers/cms/section_nodes_helper_rb.html +101 -0
  263. data/doc/app/files/app/models/abstract_file_block_rb.html +101 -0
  264. data/doc/app/files/app/models/attachment_rb.html +109 -0
  265. data/doc/app/files/app/models/category_rb.html +101 -0
  266. data/doc/app/files/app/models/category_type_rb.html +101 -0
  267. data/doc/app/files/app/models/connector_rb.html +101 -0
  268. data/doc/app/files/app/models/content_type_group_rb.html +101 -0
  269. data/doc/app/files/app/models/content_type_rb.html +101 -0
  270. data/doc/app/files/app/models/dynamic_view_rb.html +101 -0
  271. data/doc/app/files/app/models/email_message_mailer_rb.html +101 -0
  272. data/doc/app/files/app/models/email_message_rb.html +101 -0
  273. data/doc/app/files/app/models/file_block_rb.html +101 -0
  274. data/doc/app/files/app/models/group_permission_rb.html +101 -0
  275. data/doc/app/files/app/models/group_rb.html +101 -0
  276. data/doc/app/files/app/models/group_section_rb.html +101 -0
  277. data/doc/app/files/app/models/group_type_permission_rb.html +101 -0
  278. data/doc/app/files/app/models/group_type_rb.html +101 -0
  279. data/doc/app/files/app/models/guest_user_rb.html +101 -0
  280. data/doc/app/files/app/models/html_block_rb.html +101 -0
  281. data/doc/app/files/app/models/image_block_rb.html +101 -0
  282. data/doc/app/files/app/models/link_rb.html +101 -0
  283. data/doc/app/files/app/models/page_partial_rb.html +101 -0
  284. data/doc/app/files/app/models/page_rb.html +101 -0
  285. data/doc/app/files/app/models/page_route_condition_rb.html +101 -0
  286. data/doc/app/files/app/models/page_route_option_rb.html +101 -0
  287. data/doc/app/files/app/models/page_route_rb.html +101 -0
  288. data/doc/app/files/app/models/page_route_requirement_rb.html +101 -0
  289. data/doc/app/files/app/models/page_template_rb.html +101 -0
  290. data/doc/app/files/app/models/permission_rb.html +101 -0
  291. data/doc/app/files/app/models/portlet_rb.html +101 -0
  292. data/doc/app/files/app/models/redirect_rb.html +101 -0
  293. data/doc/app/files/app/models/section_node_rb.html +101 -0
  294. data/doc/app/files/app/models/section_rb.html +101 -0
  295. data/doc/app/files/app/models/site_rb.html +101 -0
  296. data/doc/app/files/app/models/tag_rb.html +101 -0
  297. data/doc/app/files/app/models/tagging_rb.html +101 -0
  298. data/doc/app/files/app/models/task_rb.html +101 -0
  299. data/doc/app/files/app/models/user_group_membership_rb.html +101 -0
  300. data/doc/app/files/app/models/user_rb.html +108 -0
  301. data/doc/app/files/app/portlets/dynamic_portlet_rb.html +101 -0
  302. data/doc/app/files/app/portlets/email_page_portlet_rb.html +101 -0
  303. data/doc/app/files/app/portlets/login_portlet_rb.html +101 -0
  304. data/doc/app/files/app/portlets/tag_cloud_portlet_rb.html +101 -0
  305. data/doc/app/files/doc/README_FOR_APP.html +127 -0
  306. data/doc/app/files/lib/acts_as_list_rb.html +101 -0
  307. data/doc/app/files/lib/browsercms_rb.html +113 -0
  308. data/doc/app/files/lib/cms/acts/content_block_rb.html +101 -0
  309. data/doc/app/files/lib/cms/authentication/controller_rb.html +101 -0
  310. data/doc/app/files/lib/cms/authentication/model_rb.html +101 -0
  311. data/doc/app/files/lib/cms/behaviors/archiving_rb.html +101 -0
  312. data/doc/app/files/lib/cms/behaviors/attaching_rb.html +101 -0
  313. data/doc/app/files/lib/cms/behaviors/categorizing_rb.html +101 -0
  314. data/doc/app/files/lib/cms/behaviors/connecting_rb.html +101 -0
  315. data/doc/app/files/lib/cms/behaviors/dynamic_attributes_rb.html +101 -0
  316. data/doc/app/files/lib/cms/behaviors/flush_cache_on_change_rb.html +101 -0
  317. data/doc/app/files/lib/cms/behaviors/hiding_rb.html +101 -0
  318. data/doc/app/files/lib/cms/behaviors/pagination_rb.html +107 -0
  319. data/doc/app/files/lib/cms/behaviors/publishing_rb.html +101 -0
  320. data/doc/app/files/lib/cms/behaviors/rendering_rb.html +101 -0
  321. data/doc/app/files/lib/cms/behaviors/searching_rb.html +101 -0
  322. data/doc/app/files/lib/cms/behaviors/soft_deleting_rb.html +101 -0
  323. data/doc/app/files/lib/cms/behaviors/taggable_rb.html +101 -0
  324. data/doc/app/files/lib/cms/behaviors/userstamping_rb.html +101 -0
  325. data/doc/app/files/lib/cms/behaviors/versioning_rb.html +101 -0
  326. data/doc/app/files/lib/cms/behaviors_rb.html +147 -0
  327. data/doc/app/files/lib/cms/caching_rb.html +101 -0
  328. data/doc/app/files/lib/cms/data_loader_rb.html +101 -0
  329. data/doc/app/files/lib/cms/extensions/action_view/base_rb.html +101 -0
  330. data/doc/app/files/lib/cms/extensions/active_record/base_rb.html +101 -0
  331. data/doc/app/files/lib/cms/extensions/active_record/connection_adapters/abstract/schema_statements_rb.html +101 -0
  332. data/doc/app/files/lib/cms/extensions/active_record/errors_rb.html +101 -0
  333. data/doc/app/files/lib/cms/extensions/active_support/cache/file_store_rb.html +101 -0
  334. data/doc/app/files/lib/cms/extensions/hash_rb.html +101 -0
  335. data/doc/app/files/lib/cms/extensions/integer_rb.html +101 -0
  336. data/doc/app/files/lib/cms/extensions/nil_rb.html +101 -0
  337. data/doc/app/files/lib/cms/extensions/string_rb.html +101 -0
  338. data/doc/app/files/lib/cms/extensions_rb.html +101 -0
  339. data/doc/app/files/lib/cms/init_rb.html +101 -0
  340. data/doc/app/files/lib/cms/routes_rb.html +101 -0
  341. data/doc/app/files/lib/initial_data_rb.html +101 -0
  342. data/doc/app/files/lib/sequence_rb.html +101 -0
  343. data/doc/app/fr_class_index.html +205 -0
  344. data/doc/app/fr_file_index.html +152 -0
  345. data/doc/app/fr_method_index.html +738 -0
  346. data/doc/app/index.html +24 -0
  347. data/doc/app/rdoc-style.css +208 -0
  348. data/doc/guides/html/build_it_yourself.html +175 -0
  349. data/doc/guides/html/deployment_guide.html +181 -0
  350. data/doc/guides/html/designer_guide.html +153 -0
  351. data/doc/guides/html/developer_guide.html +266 -0
  352. data/doc/guides/html/files/javascripts/code_highlighter.js +188 -0
  353. data/doc/guides/html/files/javascripts/guides.js +7 -0
  354. data/doc/guides/html/files/javascripts/highlighters.js +90 -0
  355. data/doc/guides/html/files/stylesheets/main.css +441 -0
  356. data/doc/guides/html/files/stylesheets/reset.css +43 -0
  357. data/doc/guides/html/files/stylesheets/style.css +13 -0
  358. data/doc/guides/html/files/stylesheets/syntax.css +31 -0
  359. data/doc/guides/html/getting_started.html +181 -0
  360. data/doc/guides/html/images/bg.png +0 -0
  361. data/doc/guides/html/images/bottom_cap.png +0 -0
  362. data/doc/guides/html/images/browsercms_logo.png +0 -0
  363. data/doc/guides/html/images/dot.png +0 -0
  364. data/doc/guides/html/images/icons/README +5 -0
  365. data/doc/guides/html/images/icons/callouts/1.png +0 -0
  366. data/doc/guides/html/images/icons/callouts/10.png +0 -0
  367. data/doc/guides/html/images/icons/callouts/11.png +0 -0
  368. data/doc/guides/html/images/icons/callouts/12.png +0 -0
  369. data/doc/guides/html/images/icons/callouts/13.png +0 -0
  370. data/doc/guides/html/images/icons/callouts/14.png +0 -0
  371. data/doc/guides/html/images/icons/callouts/15.png +0 -0
  372. data/doc/guides/html/images/icons/callouts/2.png +0 -0
  373. data/doc/guides/html/images/icons/callouts/3.png +0 -0
  374. data/doc/guides/html/images/icons/callouts/4.png +0 -0
  375. data/doc/guides/html/images/icons/callouts/5.png +0 -0
  376. data/doc/guides/html/images/icons/callouts/6.png +0 -0
  377. data/doc/guides/html/images/icons/callouts/7.png +0 -0
  378. data/doc/guides/html/images/icons/callouts/8.png +0 -0
  379. data/doc/guides/html/images/icons/callouts/9.png +0 -0
  380. data/doc/guides/html/images/icons/caution.png +0 -0
  381. data/doc/guides/html/images/icons/example.png +0 -0
  382. data/doc/guides/html/images/icons/home.png +0 -0
  383. data/doc/guides/html/images/icons/important.png +0 -0
  384. data/doc/guides/html/images/icons/next.png +0 -0
  385. data/doc/guides/html/images/icons/note.png +0 -0
  386. data/doc/guides/html/images/icons/prev.png +0 -0
  387. data/doc/guides/html/images/icons/tip.png +0 -0
  388. data/doc/guides/html/images/icons/up.png +0 -0
  389. data/doc/guides/html/images/icons/warning.png +0 -0
  390. data/doc/guides/html/images/top_cap.png +0 -0
  391. data/doc/guides/html/images/top_cap_content.png +0 -0
  392. data/doc/guides/html/index.html +168 -0
  393. data/doc/guides/html/installing_modules.html +181 -0
  394. data/doc/guides/html/user_guide.html +266 -0
  395. data/lib/cms/behaviors/attaching.rb +1 -1
  396. data/lib/cms/behaviors/rendering.rb +1 -1
  397. data/lib/cms/behaviors/taggable.rb +2 -1
  398. data/lib/cms/behaviors/versioning.rb +1 -1
  399. data/lib/cms/init.rb +4 -4
  400. data/lib/tasks/cms.rake +16 -42
  401. data/public/images/cms/buttons/button_cap_off_middle.gif +0 -0
  402. data/public/images/cms/buttons/button_left_bg.png +0 -0
  403. data/public/images/cms/buttons/button_off_middle.png +0 -0
  404. data/public/images/cms/nav_admin.gif +0 -0
  405. data/public/images/cms/nav_admin_h.gif +0 -0
  406. data/public/images/cms/nav_admin_on.gif +0 -0
  407. data/public/images/cms/nav_content_library.gif +0 -0
  408. data/public/images/cms/nav_content_library_h.gif +0 -0
  409. data/public/images/cms/nav_content_library_on.gif +0 -0
  410. data/public/images/cms/nav_dash.gif +0 -0
  411. data/public/images/cms/nav_dash_h.gif +0 -0
  412. data/public/images/cms/nav_dash_on.gif +0 -0
  413. data/public/images/cms/nav_sitemap.gif +0 -0
  414. data/public/images/cms/nav_sitemap_h.gif +0 -0
  415. data/public/images/cms/nav_sitemap_on.gif +0 -0
  416. data/public/stylesheets/cms/administration.css +91 -91
  417. data/public/stylesheets/cms/block.css +25 -25
  418. data/public/stylesheets/cms/buttons.css +120 -111
  419. data/public/stylesheets/cms/content_library.css +2 -1
  420. data/public/stylesheets/cms/content_types.css +3 -3
  421. data/public/stylesheets/cms/dashboard.css +118 -118
  422. data/public/stylesheets/cms/data_table.css +155 -155
  423. data/public/stylesheets/cms/form_layout.css +269 -269
  424. data/public/stylesheets/cms/jquery.contextMenu.css +61 -61
  425. data/public/stylesheets/cms/login.css +77 -77
  426. data/public/stylesheets/cms/menu.css +116 -116
  427. data/public/stylesheets/cms/nav.css +98 -111
  428. data/public/stylesheets/cms/page_toolbar.css +134 -134
  429. data/public/stylesheets/cms/sitemap.css +31 -15
  430. data/rails_generators/content_block/content_block_generator.rb +4 -9
  431. data/rails_generators/content_block/templates/_form.html.erb +3 -1
  432. data/rails_generators/portlet/portlet_generator.rb +2 -6
  433. data/rails_generators/portlet/templates/_form.html.erb +1 -0
  434. data/templates/blank.rb +30 -0
  435. data/templates/demo.rb +28 -0
  436. data/templates/module.rb +945 -0
  437. data/test/functional/cms/connectors_controller_test.rb +12 -1
  438. data/test/functional/cms/portlets_controller_test.rb +10 -0
  439. data/test/unit/behaviors/taggable_test.rb +19 -0
  440. data/test/unit/helpers/menu_helper_test.rb +72 -1
  441. data/test/unit/lib/generators_test.rb +21 -3
  442. data/test/unit/models/connector_test.rb +16 -0
  443. data/test/unit/models/sections_test.rb +4 -0
  444. metadata +380 -2
data/doc/guides/html/installing_modules.html ADDED
@@ -0,0 +1,181 @@
1
+ <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
2
+ <html xmlns="http://www.w3.org/1999/xhtml" lang="en" xml:lang="en">
3
+ <head>
4
+ <meta http-equiv="Content-Type" content="text/html; charset=UTF-8" />
5
+ <title>How to Install a Module</title>
6
+ <link rel="stylesheet" type="text/css" href="files/stylesheets/syntax.css" />
7
+ <script type="text/javascript" src="files/javascripts/code_highlighter.js"></script>
8
+ <script type="text/javascript" src="files/javascripts/highlighters.js"></script>
9
+ <style type="text/css">
10
+ body {
11
+ background: #FFFFFF url(images/bg.png) repeat-x scroll 0 0;
12
+ font-family: "Trebuchet MS", Helvetica, Verdana, Arial, sans-serif;
13
+ margin: 0;
14
+ padding: 0;
15
+ }
16
+
17
+ #page {
18
+ margin: 0 auto;
19
+ text-align: left;
20
+ width: 1000px;
21
+ }
22
+
23
+ #header {
24
+ height: 110px;
25
+ }
26
+
27
+ div.top_cap {
28
+ background: transparent url(images/top_cap.png) no-repeat scroll 0 0;
29
+ height: 10px;
30
+ }
31
+
32
+ #contentwrap {
33
+ background: transparent url(images/dot.png) repeat scroll 0 0;
34
+ float: left;
35
+ width: 1000px;
36
+ }
37
+
38
+ div.bottom_cap {
39
+ background: transparent url(images/bottom_cap.png) no-repeat scroll 0 0;
40
+ height: 9px;
41
+ }
42
+
43
+ div.top_cap_content {
44
+ background: transparent url(images/top_cap_content.png) no-repeat scroll 0 0;
45
+ height: 5px;
46
+ }
47
+
48
+ #content {
49
+ background-color: #FFFFFF;
50
+ margin: 0 5px;
51
+ padding: 0 10px;
52
+ }
53
+
54
+ div.title {
55
+ padding: 20px;
56
+ }
57
+
58
+ div.title h1 {
59
+ border-bottom: 3px solid #505358;
60
+ color: #FFFFFF;
61
+ font-size: 24pt;
62
+ font-weight: normal;
63
+ line-height: 1;
64
+ margin: 0 0 10px;
65
+ padding-bottom: 10px;
66
+ }
67
+
68
+ td.sidebar {
69
+ font-size: 8pt;
70
+ width: 165px;
71
+ padding: 5px;
72
+ }
73
+
74
+ td.sidebar ol {
75
+ margin-left: 20px;
76
+ padding: 0;
77
+ line-height: 1.5;
78
+ }
79
+
80
+ td.sidebar ol li {
81
+ margin: 0;
82
+ padding: 0;
83
+ }
84
+
85
+ td.sidebar ol li ul {
86
+ list-style-type: none;
87
+ padding-left: 10px;
88
+ }
89
+
90
+ td.guides {
91
+ font-size: 10pt;
92
+ width: 800px;
93
+ padding: 10px;
94
+ }
95
+
96
+ .code_container {
97
+ padding: 10px;
98
+ background: #eee;
99
+ border: 1px solid #ccc;
100
+ overflow: auto;
101
+ width: 760px;
102
+ }
103
+
104
+ pre, code {
105
+ overflow: auto;
106
+ white-space:pre;
107
+ }
108
+
109
+ </style>
110
+ </head>
111
+ <body>
112
+ <div id="page">
113
+ <div id="header">
114
+ <a href="index.html"><img style="border:0px" src="images/browsercms_logo.png" alt="BrowserCMS"/></a>
115
+ </div>
116
+ <div id="main">
117
+ <div class="top_cap"></div>
118
+ <div id="contentwrap">
119
+ <div class="title">
120
+ <h1>How to Install a Module</h1>
121
+ </div>
122
+ <div class="top_cap_content"></div>
123
+ <div id="content">
124
+ <table width="100%" cellpadding="0" cellspacing="0" border="0">
125
+ <tr>
126
+ <td class="sidebar" valign="top">
127
+ <div id="subCol">
128
+ <h3 class="chapter"><img src="images/chapters_icon.gif" alt="" />Chapters</h3>
129
+ <ol class="chapters">
130
+ <li><a href="#installation">Installation</a><ul><li><a href="#build-and-install-the-gem-from-source">Build and install the gem from source</a></li><li><a href="#adding-the-module-to-your-project">Adding the Module to your project</a></li></ul></li></ol></div>
131
+ </td>
132
+ <td class="guides">
133
+ <h2>How to Install a Module</h2>
134
+ <p>This guide covers how to download and install a module for BrowserCMS. With BrowserCMS, modules are packaged as Ruby Gems, which contain the code to add new behavior to a BrowserCMS project. Installing a module consists of several steps, including:</p>
135
+ <ol>
136
+ <li>Getting the Gem installed</li>
137
+ <li>Telling BrowserCMS to use that Gem</li>
138
+ <li>Pulling the module specific code into your project (like migrations)</li>
139
+ <li>Running migrations</li>
140
+ </ol>
141
+ <p>Once you have done the above steps, you should have access to the Content blocks and portlets that each module provides, and you can add them to your pages.</p>
142
+ <h3 id="installation">1 Installation</h3>
143
+ <p>This module assumes you are going to be building the module from source code, and installing to a project locally to your computer. Let&#8217;s assume you want to install the News module, who&#8217;s project name (and gem name) is &#8216;bcms_news&#8217;. If you want to install other modules, just substitute the name of the module you want for &#8216;bcms_news&#8217;.</p>
144
+ <h4 id="build-and-install-the-gem-from-source">1.1 Build and install the gem from source</h4>
145
+ <p>This assumes you have the latest copy of the code from github on your machine, in a directory <tt>~/my_projects_dir/bcms_news_dir</tt>.</p>
146
+ <div class="code_container"><code class="html">$ cd ~/my_projects_dir/bcms_news
147
+ $ gem build bcms_news.gemspec
148
+ $ sudo gem install bcms_news-1.0.0.gem</code></div>
149
+ <p>At this point, the News module gem should be installed as a gem on your system, and can be added to your projects.</p>
150
+ <h4 id="adding-the-module-to-your-project">1.2 Adding the Module to your project</h4>
151
+ <p>In your BrowserCMS application, do the following steps.</p>
152
+ <h5 id="edit-the-confingenvironmentrb-file">1.2.1 Edit the confing/environment.rb file</h5>
153
+ <div class="code_container"><code class="ruby">config.gem 'browsercms'
154
+ # Add this next line after the browsercms gem
155
+ config.gem &quot;bcms_news&quot;</code></div>
156
+ <h5 id="edit-the-routesrb-file">1.2.2 Edit the routes.rb file</h5>
157
+ <div class="code_container"><code class="ruby"># Add this route. It must be before the core browser_cms route.
158
+ map.routes_for_bcms_news
159
+ map.routes_for_browser_cms</code></div>
160
+ <h5 id="install-the-new-module-code">1.2.3 Install the new module code</h5>
161
+ <p>From the root directory of your cms project, run:</p>
162
+ <div class="code_container"><code class="html">$ script/generate browser_cms</code></div>
163
+ <p>This will copy all the necessary views and migrations from the gems into your local project. You should messages checking to see if files already exist or were created.</p>
164
+ <h5 id="run-migrations-and-start-the-server">1.2.4 Run migrations and start the server</h5>
165
+ <p>Modules will often add new data types, like content blocks, so you need to run the migrations to add them to your project.</p>
166
+ <div class="code_container"><code class="html">$ rake db:migrate
167
+ $ script/server</code></div>
168
+ <h5 id="add-new-content-to-your-site">1.2.5 Add New Content to your Site</h5>
169
+ <p>Most modules will come with a few new types of content, either a new Content Block and one or more Portlets, which are designed to display those Content Blocks in interesting ways. To discover what new contents have been added, you can look at the Content Library for a new group (like &#8216;News&#8217;) or add a new Portlet, which will list all available portlets in the system.</p>
170
+ </td>
171
+ </tr>
172
+ </table>
173
+ </div>
174
+ </div>
175
+ <br clear="all"/>
176
+ <div class="bottom_cap"></div>
177
+ </div>
178
+ </div>
179
+ </body>
180
+ </html>
181
+
data/doc/guides/html/user_guide.html ADDED
@@ -0,0 +1,266 @@
1
+ <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
2
+ <html xmlns="http://www.w3.org/1999/xhtml" lang="en" xml:lang="en">
3
+ <head>
4
+ <meta http-equiv="Content-Type" content="text/html; charset=UTF-8" />
5
+ <title>User Guide for BrowserCMS</title>
6
+ <link rel="stylesheet" type="text/css" href="files/stylesheets/syntax.css" />
7
+ <script type="text/javascript" src="files/javascripts/code_highlighter.js"></script>
8
+ <script type="text/javascript" src="files/javascripts/highlighters.js"></script>
9
+ <style type="text/css">
10
+ body {
11
+ background: #FFFFFF url(images/bg.png) repeat-x scroll 0 0;
12
+ font-family: "Trebuchet MS", Helvetica, Verdana, Arial, sans-serif;
13
+ margin: 0;
14
+ padding: 0;
15
+ }
16
+
17
+ #page {
18
+ margin: 0 auto;
19
+ text-align: left;
20
+ width: 1000px;
21
+ }
22
+
23
+ #header {
24
+ height: 110px;
25
+ }
26
+
27
+ div.top_cap {
28
+ background: transparent url(images/top_cap.png) no-repeat scroll 0 0;
29
+ height: 10px;
30
+ }
31
+
32
+ #contentwrap {
33
+ background: transparent url(images/dot.png) repeat scroll 0 0;
34
+ float: left;
35
+ width: 1000px;
36
+ }
37
+
38
+ div.bottom_cap {
39
+ background: transparent url(images/bottom_cap.png) no-repeat scroll 0 0;
40
+ height: 9px;
41
+ }
42
+
43
+ div.top_cap_content {
44
+ background: transparent url(images/top_cap_content.png) no-repeat scroll 0 0;
45
+ height: 5px;
46
+ }
47
+
48
+ #content {
49
+ background-color: #FFFFFF;
50
+ margin: 0 5px;
51
+ padding: 0 10px;
52
+ }
53
+
54
+ div.title {
55
+ padding: 20px;
56
+ }
57
+
58
+ div.title h1 {
59
+ border-bottom: 3px solid #505358;
60
+ color: #FFFFFF;
61
+ font-size: 24pt;
62
+ font-weight: normal;
63
+ line-height: 1;
64
+ margin: 0 0 10px;
65
+ padding-bottom: 10px;
66
+ }
67
+
68
+ td.sidebar {
69
+ font-size: 8pt;
70
+ width: 165px;
71
+ padding: 5px;
72
+ }
73
+
74
+ td.sidebar ol {
75
+ margin-left: 20px;
76
+ padding: 0;
77
+ line-height: 1.5;
78
+ }
79
+
80
+ td.sidebar ol li {
81
+ margin: 0;
82
+ padding: 0;
83
+ }
84
+
85
+ td.sidebar ol li ul {
86
+ list-style-type: none;
87
+ padding-left: 10px;
88
+ }
89
+
90
+ td.guides {
91
+ font-size: 10pt;
92
+ width: 800px;
93
+ padding: 10px;
94
+ }
95
+
96
+ .code_container {
97
+ padding: 10px;
98
+ background: #eee;
99
+ border: 1px solid #ccc;
100
+ overflow: auto;
101
+ width: 760px;
102
+ }
103
+
104
+ pre, code {
105
+ overflow: auto;
106
+ white-space:pre;
107
+ }
108
+
109
+ </style>
110
+ </head>
111
+ <body>
112
+ <div id="page">
113
+ <div id="header">
114
+ <a href="index.html"><img style="border:0px" src="images/browsercms_logo.png" alt="BrowserCMS"/></a>
115
+ </div>
116
+ <div id="main">
117
+ <div class="top_cap"></div>
118
+ <div id="contentwrap">
119
+ <div class="title">
120
+ <h1>User Guide for BrowserCMS</h1>
121
+ </div>
122
+ <div class="top_cap_content"></div>
123
+ <div id="content">
124
+ <table width="100%" cellpadding="0" cellspacing="0" border="0">
125
+ <tr>
126
+ <td class="sidebar" valign="top">
127
+ <div id="subCol">
128
+ <h3 class="chapter"><img src="images/chapters_icon.gif" alt="" />Chapters</h3>
129
+ <ol class="chapters">
130
+ <li><a href="#basic-concepts">Basic Concepts</a><ul></ul></li><li><a href="#common-tasks">Common Tasks</a><ul><li><a href="#logging-into-the-cms">Logging into the <span class="caps">CMS</span></a></li><li><a href="#editing-the-home-page">Editing the home page</a></li><li><a href="#publishing-pages">Publishing pages</a></li><li><a href="#adding-a-new-page">Adding a new page</a></li><li><a href="#adding-new-text-content-to-a-page">Adding new text content to a page</a></li><li><a href="#adding-images-and-files-to-pages">Adding images and files to pages</a></li><li><a href="#finding-a-page-to-edit">Finding a page to edit</a></li><li><a href="#reverting-a-page">Reverting a page</a></li><li><a href="#reorganize-a-sites-navigation">Reorganize a site&#8217;s navigation</a></li><li><a href="#setting-up-restricted-sections">Setting up restricted sections</a></li><li><a href="#setting-up-workflow">Setting up Workflow</a></li><li><a href="#using-my-dashboard">Using My Dashboard</a></li><li><a href="#adding-dynamic-content-via-portlets">Adding dynamic content via portlets</a></li></ul></li></ol></div>
131
+ </td>
132
+ <td class="guides">
133
+ <h2>User Guide for BrowserCMS</h2>
134
+ <h3>What to Expect</h3>
135
+ <p>This guide covers how to use BrowserCMS to build and manage websites. After reading it, you should understand how to:</p>
136
+ <ul>
137
+ <li>Create new pages</li>
138
+ <li>Organize your site navigation via the sitemap.</li>
139
+ <li>Place content on pages.</li>
140
+ <li>Dynamically display content on pages using portlets.</li>
141
+ <li>Create and assign permissions to users.</li>
142
+ </ul>
143
+ <p>This guide is aimed at people who are managing sites using BrowserCMS, as opposed to programmers who want to <a href="developer_guide.html">customize it</a>, or designers who want to <a href="designer_guide.html">create new designs</a> for a site.</p>
144
+ <h3>What not to expect</h3>
145
+ <p>This document assumes that users have a working copy of BrowserCMS to play with, either on their local machine, or on a demo site. We don&#8217;t cover how to install <span class="caps">CMS</span> here, so see the <a href="getting_started.html">Getting Started</a> Guide in order to get up and running.</p>
146
+ <p>In addition, an installation of BrowserCMS will have several templates already installed. The &#8216;theme&#8217; might be the default BrowserCMS theme, or a custom theme designed for a specific client. This document does not cover how to design and create new themes/templates, but focuses on the day to day work that content managers will need to do.</p>
147
+ <h3 id="basic-concepts">1 Basic Concepts</h3>
148
+ <p>There are several concepts which underly how BrowserCMS works. To be productive, users of BrowserCMS should ideally understand these ideas:</p>
149
+ <ul>
150
+ <li><strong>Pages</strong> &#8211; Visitors experience your site primarily via pages. Pages are really compound documents, consisting of more than one editable area of content. The allows for intricate design, without needing to be edited via single giant <span class="caps">HTML</span> area.</li>
151
+ <li><strong>Content Blocks</strong> &#8211; Blocks are the most granular bits of content in a system. Pages usually have one or more blocks of content associated with them. Content blocks can be anything from a simple fragment of <span class="caps">HTML</span>, to a News Article (which might have multiple data fields like name, body and summary), to portlets, which dynamically display other types of content.</li>
152
+ <li><strong>Portlets</strong> &#8211; Sometimes you don&#8217;t want to manually place all the content on your site. You want to set up some rules, so that when new content is entered, it appears in multiple places. Portlets are generally how that gets done. Portlets are really just a slightly special version of blocks, which generally query for other blocks, and then format them for display.</li>
153
+ <li><strong>Sections</strong> &#8211; Each page lives in a section. Sections the primary way pages are organized. Menus are usually dynamically constructed based off the hierarchy of sections and pages. Sections also handle security, where individual groups are allowed to see pages within a given section. Sections and pages can be reordered by using the Site Map tab.</li>
154
+ <li><strong>Templates</strong> &#8211; Each page has a template, which handles governs the styles and layout for that page. A template will determine what areas of the page are editable, how many columns it has and how the navigation will work. A website will usually have multiple templates (i.e. Home Page and Subpage) which provide different layout choices for users when they create new pages.</li>
155
+ <li><strong>Users and Groups</strong> &#8211; Security is handled via users and groups. A user might represent a &#8216;public&#8217; user, who can access some sections of your website (like a &#8216;Members only section&#8217;). Or they might be a &#8216;<span class="caps">CMS</span>&#8217; user who has the ability to make changes to the content via the <span class="caps">CMS</span> editing tools. Each user can be part of multiple groups, which define what they can do, including editing pages, viewing content or publishing new pages.</li>
156
+ </ul>
157
+ <h3 id="common-tasks">2 Common Tasks</h3>
158
+ <p>This section will cover some of the more frequent tasks that site managers will need to undertake in order to manage their website. For the purposes of this section, all examples assume a locally running copy of BrowserCMS, accessed as http://localhost:3000. A site hosted elsewhere might be running at http://yourcms.yourcompany.com.</p>
159
+ <h4 id="logging-into-the-cms">2.1 Logging into the <span class="caps">CMS</span></h4>
160
+ <p>To access that administrative portions of a <span class="caps">CMS</span>, you have to go to the admin login page. To do this, add /cms to your website&#8217;s <span class="caps">URL</span>. Working locally, this would be http://localhost:3000. From this page, you can log in with your username and password. For a local site, this will be username = cmsadmin and password = cmsadmin. For a live site, this will have been randomly set during install.</p>
161
+ <p>After you log in, you will be sent to the dashboard (/cms/dashboard). The details of this page will be covered later, but the dashboard serves a summary of content in various workflow stages. From here, you can jump to other sections of <span class="caps">CMS</span>.</p>
162
+ <h4 id="editing-the-home-page">2.2 Editing the home page</h4>
163
+ <p>To understand how editing pages in the <span class="caps">CMS</span> works, let&#8217;s jump over to the homepage. The quickest way to do that is to click on the BrowserCMS logo in the top left. This will always take you to the home page for your site. When you visit a page in BrowserCMS, and are logged in as editor, you will see the page exactly as a visiter would, with the addition of a toolbar at the top of the page. This toolbar gives you the tools/buttons necessary to make changes to pages, or jump to other <span class="caps">CMS</span> admin tabs.</p>
164
+ <h5 id="in-context-editing">2.2.1 In Context Editing</h5>
165
+ <p>One of the key concepts to make page editing easier in BrowserCMS is called &#8216;In Context Editing&#8217;. It allows you to browse the site as a visitor would, and then edit content directly on the page. By default, you can&#8217;t see the editable areas of a page (called &#8216;Containers&#8217;), because the Visual Editor is turned off. To show the containers, click the &#8216;Turn On&#8217; button on the right side of the toolbar, which turns on the visual editor. You should now see the containers highlighted on the page. The templates for each page determine what areas of the page are editable. Clicking the &#8216;Turn Off&#8217; button will hide the containers again, giving you a more accurate view of what the finished page will look like.</p>
166
+ <h5 id="containers">2.2.2 Containers</h5>
167
+ <p>A container is marked by a box with a grey header, with several buttons on it. Each container has two controls, one to Add new content to that container (The + icon) and another to place existing content into the container. It also has a status indicator which shows if any content blocks in that container are in draft mode. Each container can hold zero or more content blocks.</p>
168
+ <h5 id="blocks">2.2.3 Blocks</h5>
169
+ <p>Each block within a container is marked with a grey border, and several buttons. Blocks can be edited, reordered using the up or down arrows, or removed from the page (which does not delete it).</p>
170
+ <h5 id="making-changes">2.2.4 Making changes</h5>
171
+ <p>To edit some existing content, pick the block you want to edit, and click the &#8216;wrench&#8217; icon. This will take you to the edit screen for that block. Most content blocks placed on pages are usually &#8216;Text&#8217; blocks, which are just pure html content, with a name for organization purposes. On the &#8216;Edit Text&#8217; page, you can change the name, or use the <span class="caps">WYSIWYG</span> editor to make changes to the content. If you want to edit the source html directly, you can change your editor preference with the toggle to the top right of the editor.</p>
172
+ <p>Once your edits are complete, you can save your changes using the Save button at the bottom of the page. This will return you to the page, where you can see how your changes look in context to the rest of your page. Your changes won&#8217;t be visible on the public site yet, so you can choose to make more changes. See the next section on how to publish changes.</p>
173
+ <h4 id="publishing-pages">2.3 Publishing pages</h4>
174
+ <p>The basic rule of publishing is that all changes need to be published before they go live. This allows editors to always see how their page is going to look, before they decide to commit their changes. Any time you alter how a page looks, the <span class="caps">CMS</span> stores a new version of that page and all its content. This happens when you add a new block to a page, make an edit or remove a block from that page. Each time a change is made to content on a page, that page will go into &#8216;Draft&#8217; status. As an editor, you will see the &#8216;latest&#8217; version of that page, but the public will continue to see the last &#8216;published&#8217; version of that page.</p>
175
+ <p>Each page has a status of either &#8216;Published&#8217; or &#8216;Draft&#8217;. When you like how your changes look, and want to publish the page, push the &#8216;Publish&#8217; button in the upper left hand corner of a page. This will makes your changes &#8216;live&#8217; and visible to the world. When a page is published, each block on that page will also be published.</p>
176
+ <h4 id="adding-a-new-page">2.4 Adding a new page</h4>
177
+ <p>To add new pages to a site, click on the Site Map tab from any where within the <span class="caps">CMS</span> admin. The Site Map page shows a tree with all the sections and pages in your site. From here, you can add new pages or sections, choose a page to edit, or reorganize the site using drag and drop to move sections around.</p>
178
+ <p>To add a new page, click on the &#8216;My Site&#8217; section at the top of the site map. Then click the &#8216;Add Page&#8217; button in the toolbar. This will add a new page to the root of the site. There are several fields to fill out the important ones are the name and templates. When you name a page, the <span class="caps">CMS</span> will generate a default relative <span class="caps">URL</span> (a path) for it. You can also choose a template via a drop down, which will show all available templates for the current site.</p>
179
+ <p>After filling out those two fields, you can click save to create the new page. After saving, you will be taken to that page, which will be blank, not having content blocks selected for it.</p>
180
+ <h4 id="adding-new-text-content-to-a-page">2.5 Adding new text content to a page</h4>
181
+ <p>When viewing a page, you can add new content to it. First, make sure the Visual Editor is turned on, so you can see the containers. Find the &#8216;Add Content&#8217; icon (+) on the container you want to add the new content to. You will then be able to choose what kind of content you want to create. Text is the most frequently used content type, and is essentially just <span class="caps">HTML</span>, including the ability to create links and include images.</p>
182
+ <p>Choosing Text will take you to the &#8216;Add New Text&#8217; screen. The first field will prompt you for a &#8216;name&#8217;. This &#8216;name&#8217; is used to help identify your content later, when you are looking for it in the Content Library. Naming Text blocks after the page they are going on is a common choice. The second field is &#8216;content&#8217;, which allows you to enter formatted text using a rich text (or <span class="caps">WYSIWYG</span>) editor. The editor has buttons for common formating options, like making text bold, copy/pasting of text (including from Microsoft Word) and creating links to other pages.</p>
183
+ <p>If you like, you can also change your text editor choice from \&#8216;Rich Text\&#8217; to \&#8216;Simple Text&#8217;, which will allow you to edit the source <span class="caps">HTML</span> directly. This choice is saved as user preference, so next time you edit content, you will use the same editor you picked.</p>
184
+ <h4 id="adding-images-and-files-to-pages">2.6 Adding images and files to pages</h4>
185
+ <p>When creating content for pages, its a common task to add images or link to files (like PDFs) in the body of the text. There are two steps to adding an image or file to a page. First you need to upload the image/file to the content library. The second is to link to or place the image within a Text block. It is possible to directly place an image or file block into a container (via the &#8216;Add New Content&#8217; option we talked about earlier) but this gives you less control over formating and placement.</p>
186
+ <h5 id="uploading-files">2.6.1 Uploading files</h5>
187
+ <p>To add an image or file to the content library, click the &#8216;Content Library&#8217; tab, and then click the &#8216;Image&#8217; or &#8216;File&#8217; menu items on the left hand side. (These content types are under the &#8216;Core&#8217; module, so you may need to click &#8216;Core&#8217; to show all the content types) Next click &#8216;Add New Content&#8217; on the main menu. From here, you can fill in all the details on your image/file, including the file on your local hard drive that you want to upload. One of the choices about creating Image and Files is which section they should be stored in. It&#8217;s a good idea to create one or more image/file galleries to keep your files organized.</p>
188
+ <p>After the file is uploaded, you can then place it on a page using a Text block.</p>
189
+ <h5 id="placing-an-image">2.6.2 Placing an image</h5>
190
+ <p>To place an image, first find the text block that you want to edit (or add). Using the &#8216;Rich Text&#8217; editor, click the &#8216;Insert/Edit Image&#8217; button. Next click &#8216;Browse Server&#8217;, which will allow you to browse through all the images in your content library. This will popup a window which gives you a sitemap view of your site. You can drill down through the sections, finding which the one where you placed your image. Once you locate the image, click the image name to select it. This will add the path to the image to the &#8216;Image Properties&#8217;, and allow you to preview the image alongside the text. You can alter the image attributes (size and alignment) or just click &#8216;Ok&#8217; to place the image.</p>
191
+ <p>At this point, the Rich Text editor should display the image embedded in the text. You can then save the Text block, and see how it looks on your page.</p>
192
+ <h5 id="placing-a-link-to-a-file">2.6.3 Placing a link to a file</h5>
193
+ <p>Placing a file is very similar to placing an image. Select the Text block to edit, and click the &#8216;Insert Link&#8217; button. On the &#8216;Link&#8217; popup window, click the &#8216;Browse Server&#8217; button. Using the Site Map browser, choose the file you want to link to, and then select it. This will paste the path to the file into the &#8216;Link&#8217; window. Click &#8216;Ok&#8217; to add the link to the Text block.</p>
194
+ <h4 id="finding-a-page-to-edit">2.7 Finding a page to edit</h4>
195
+ <p>BrowserCMS features two ways to locate pages to make changes to. The first one is just browsing around the site, using the same navigation that your site users would. The second is the by using the Sitemap.</p>
196
+ <h5 id="navigating-to-find-pages">2.7.1 Navigating to find pages</h5>
197
+ <p>When an editor is logged in, they can browse around the site using the same menus and links that a guest would. Each page will appear with a toolbar, which only editors see, which allows you to make changes to pages and their properties.</p>
198
+ <h5 id="using-the-sitemap-to-find-pages">2.7.2 Using the Sitemap to find pages</h5>
199
+ <p>The Site Map allows editors to see a more conventional &#8216;file and folder&#8217; metaphor to browse through the structure of the site. Clicking the &#8216;Sitemap&#8217; tab will take editors to this view. Once on the sitemap, editors can expand/collapse sections by clicking on the +/- buttons. They can drill down into each section, to locate the page they want to make changes to. Once the page is located, either select the page and click &#8216;Edit Page&#8217; on the toolbar, or just double click the page name. Both take users to the &#8216;Edit Page&#8217; view, which allows them to modify the page content.</p>
200
+ <h4 id="reverting-a-page">2.8 Reverting a page</h4>
201
+ <p>Mistakes happen. Sometimes you make a change to a page, and you don&#8217;t like how it looks, or you just want to go back to last week&#8217;s version. To roll back a page to an earlier version, you must first edit that page (either by navigating to or by the sitemap). Select the &#8216;List Versions&#8217; button from the toolbar. This will show the complete history of the page, along with who made changes, when the change occured, and note about what change happened in that version.</p>
202
+ <p>To see what an older version looked like, select a version, and click &#8216;View&#8217; on the toolbar. (Recommended Tip: Open the version in a new tab in your browser, by Ctrl-Click on PC, or Command-Clicking on Mac. This will let you compare several versions side by side.) If you like that version, you can revert to it in two ways.</p>
203
+ <p>From the &#8216;List Versions&#8217; page, you can revert by selecting the version, then clicking &#8216;Revert&#8217;. If you are viewing an older version, you can revert by clicking the &#8216;Revert to This Version&#8217;. In both cases, it will restore the page to what it looked like in that version, and will mark the page as &#8216;Draft&#8217;. Once the editor has reviewed the changes, they can publish it.</p>
204
+ <h5 id="reverting-gotchas">2.8.1 Reverting Gotchas</h5>
205
+ <p>Reverting can be a bit tricky to understand. The basic challenge comes from the fact that both pages and block have their own versions, and blocks can be shared across pages. Consider the example of two pages, Page A and Page B, which both share a Text Block &#8216;C&#8217;. Every change to &#8216;C&#8217; will also create a new version of &#8216;A&#8217; and &#8216;B&#8217;. Reverting page &#8216;A&#8217; will also likely revert page &#8216;B&#8217;. Since reverting a page puts it into Draft, you now have two pages in draft mode. You need to publish both of them to make their changes live. This might be manageable for two pages, but imagine you had a Text called &#8216;footer&#8217; which was shared across 20 pages.</p>
206
+ <p>See `Bulk Publishing&#8217; below for details on how to publish multiple pages at once.</p>
207
+ <h4 id="reorganize-a-sites-navigation">2.9 Reorganize a site&#8217;s navigation</h4>
208
+ <p>There are two ways that BrowserCMS supports navigation. The first is that navigation is manually added as <span class="caps">HTML</span> to templates. This is suitable for &#8216;Fixed Space&#8217; navigation, which might need to be exactly 400 pixels wide and contain exactly 4 menu items, potentially using images for buttons. The second is using dynamic navigation, which can easily grow as the site architecture does. This is more suitable for sub-sections of the site. BrowserCMS allows editors to dynamically render menus based off pages in the sitemap.</p>
209
+ <h5 id="understanding-how-dynamic-navigation-works">2.9.1 Understanding how dynamic navigation works</h5>
210
+ <p>When developers create templates, they can set up menus so that they dynamically link to pages in the sitemap. Menus will show both pages and sections, and can show go one or more levels deep, which reflects how users are &#8216;drilling down&#8217; into the site architecture. By default, when an editor adds a page or section to the sitemap, under a specific section, a link to that page will automatically be added to the dynamic navigation. For both pages and sections, you can have the option to &#8216;Hide from menus&#8217;, which you can do by editing the properties of either pages or sections. Hiding a page from a menu means its still accessible to the public (if the user knows the <span class="caps">URL</span>), but just doesn&#8217;t appear in the menus.</p>
211
+ <h5 id="moving-pagessections-in-the-sitemap">2.9.2 Moving pages/sections in the sitemap</h5>
212
+ <p>When pages and sections are created, they are added last in their parent section. They can be reordered though from the Sitemap, by dragging and dropping. To move a page or section, click-hold and drag the page/section where you want it to be. This allows editors to both reorder pages within a specific menu, or move it to another area of the site entirely.</p>
213
+ <p>Dropping an item onto a page will place it &#8216;after&#8217; that page. Dropping an item onto a section will put it in that section, as the last item. Be aware that moving pages will immediately make changes in how the dynamic site menus appear (there is no &#8216;publish&#8217; step needed).</p>
214
+ <h4 id="setting-up-restricted-sections">2.10 Setting up restricted sections</h4>
215
+ <p>It&#8217;s a common task to want to restrict specific users from being able to see certain pages. This might include creating a &#8216;members&#8217; section, where only registered and approved users can see the content. BrowserCMS allows editors/admins to restrict user access based on sections. Individual pages get their security from their immediate parent. For example, if there is a section called &#8216;Member Only&#8217;, which a &#8216;Guest&#8217; cannot see, all pages in that section will be block, and guests (unregistered users) that try to access those URLs will be sent to the &#8216;Access Denied&#8217; page.</p>
216
+ <h5 id="creating-the-groups">2.10.1 Creating the groups</h5>
217
+ <p>The first step to secure a section is to set up the groups who are allowed to see it. An administrator can create a new group by clicking the &#8216;Administration&#8217; tab, then selecting the &#8216;Groups&#8217; item from the left menu. Click the &#8216;Add Group&#8217; button, give the group a name (&#8216;Members&#8217;), and choose &#8216;Registered Public User&#8217; as the group type. By default, this group will able to view all sections within the site. After saving the group, you can alter which sections a user can see, by clicking the name of the group. In this case, the new &#8216;Member&#8217; group&#8217;s permissions are fine.</p>
218
+ <h5 id="adding-users">2.10.2 Adding users</h5>
219
+ <p>The next step is to create a user in the &#8216;Member&#8217; group. On the &#8216;Administration&#8217; tab, click the &#8216;Users&#8217; menu item on the left menu, and click &#8216;Add User&#8217; on the toolbar. Fill in the basic user information (name, username, email and password) and check the newly added &#8216;Members&#8217; group (but no others)</p>
220
+ <h5 id="restricting-the-sections">2.10.3 Restricting the sections</h5>
221
+ <p>The next step is to add the new section, which will be restricted so that only users who are in the &#8216;Member&#8217; group can see them. Go to the sitemap, select the &#8216;My Site&#8217; (which is the root of the site) and click &#8216;Add Section&#8217;. Name the section &#8216;Members Only&#8217;, and then uncheck all public permissions except for &#8216;Member&#8217;. Next add a page to this section and publish it.</p>
222
+ <p>Now, when users who aren&#8217;t logged in (Guests) try to visit any pages in the &#8216;Members Only&#8217; section, they will be redirected to the Accessed Denied page.</p>
223
+ <h4 id="setting-up-workflow">2.11 Setting up Workflow</h4>
224
+ <p>When the number of contributors to a website grows, it may be necessary to restrict who has rights to publish content. This would allow for multiple editors to contribute and edit content, but content would be passed to one or more `publishers&#8217; in order to commit the changes publicly.
225
+ Workflow in BrowserCMS has several concepts which make it work:</p>
226
+ <ul>
227
+ <li>Rights &#8211; Who can edit and who can publish?</li>
228
+ <li>Tasking &#8211; Who the work is assigned to?</li>
229
+ <li>Notification &#8211; How do people know they have new content to look at.</li>
230
+ </ul>
231
+ <p>This section covers how to create a simple workflow, that covers two kinds of groups of people.</p>
232
+ <ul>
233
+ <li>Contributors: These people should be able to edit pages and content, but should not be able to publish them.</li>
234
+ <li>Publishers: These people should be able to edit pages/content, and can publish them.</li>
235
+ </ul>
236
+ <h5 id="basic-contributor-and-editor-workflow">2.11.1 Basic Contributor and Editor workflow</h5>
237
+ <p>The first step is to create two new groups, both of which should be of type `<span class="caps">CMS</span> User&#8217;. One should be called &#8216;Contributor&#8217;, and should only have the `Edit Content&#8217; permission. The second group should be called `Publisher&#8217;, and should have `Edit Content&#8217; and `Publish Content&#8217; permissions. Next create two users, and assign one of them to each group.</p>
238
+ <p>The user in the Contributor group, will be able to make changes to pages and blocks, but will not be able to publish it themselves. When they are done with a page, on the &#8216;Edit Page&#8217; view, they can use the &#8216;Assign&#8217; button to pass the page to somebody who has publishing rights. Assigning a page provides a drop down with all users who have &#8216;Edit Content&#8217; permissions. The contributor can choose the assign to the &#8216;Publisher&#8217;, give it a due date and a comment, and then assign the page. This will notify the &#8216;Publisher&#8217; via email they have a new task assigned to them, along with the <span class="caps">URL</span> to the page.</p>
239
+ <p>The &#8216;Publisher&#8217; can then log in, find the page they want to review, make sure the changes are acceptable, then publish the page. Once they are down with their task, they can click the &#8216;Complete Task&#8217; button to close the task out. In addition, editors and publishers can always find what open tasks they have by going to the &#8216;My Dashboard&#8217;.</p>
240
+ <h4 id="using-my-dashboard">2.12 Using My Dashboard</h4>
241
+ <p>The dashboard is the landing page for editors when they log in. It has two main areas, one shows all pages currently in draft. The other shows open tasks assigned to the current users.</p>
242
+ <h5 id="bulk-publishing">2.12.1 Bulk publishing</h5>
243
+ <p>Some operations in the <span class="caps">CMS</span> can put multiple pages into Draft mode as a side effect. This includes making an edit to a block which is shared across multiple pages, as well as reverting a page with shared blocks on it. The &#8216;Page Drafts&#8217; panel shows all pages in the <span class="caps">CMS</span> which are currently in draft mode. An editor can choose to review each page to make sure it looks right, by clicking on the name of the page. Or they can just select all pages they want to publish via the checkbox, and then click `Publish Selected&#8217;.</p>
244
+ <h5 id="tasks">2.12.2 Tasks</h5>
245
+ <p>All of the open tasks that are assigned to a user will appear on that user&#8217;s dashboard, in the &#8216;Tasks&#8217; panel. Users can click on the name of the page to review it, and either complete the task, or assign it someone else.</p>
246
+ <h4 id="adding-dynamic-content-via-portlets">2.13 Adding dynamic content via portlets</h4>
247
+ <p>For most sites, the majority of the content will be placed directly on pages using Text blocks. Another alternative is to use portlets, which can dynamically select and render content. Portlets are usually part of individual modules, and are used to find and display content from that module. For example, the &#8216;News&#8217; module comes with several portlets, designed to find News Articles by specific criteria. One portlet may display a single Article (using an id parameter in the <span class="caps">URL</span>), while another may show the headlines to all Articles, chronologically ordered.</p>
248
+ <p>Portlets are one of the primary extension points of BrowserCMS, which allows programmers to create new dynamic behavior and allow it to be placed on pages alongside static content. Each portlet will have several attributes which allow users to configure the portlet. These attributes might include a name, max # of results to display, and a template to allow users to change how the portlet displays. This section assumes the News Module has been installed, and walks through the placing and configuring of a portlet.</p>
249
+ <h5 id="placing-and-configuring-portlet-on-a-page">2.13.1 Placing and configuring portlet on a page</h5>
250
+ <p>Start by creating a new page. Select the &#8216;Add New Content&#8217; icon in the container you would like to add the portlet to. On the &#8216;Select Content Screen&#8217;, choose the &#8216;Portlet&#8217; type. Then choose which type of portlet you would like to add (Choose the News Archive portlet). Give the portlet a name, leave the categories empty and use the default template.</p>
251
+ <p>The News Archive portlet is designed to show a list of New Article blocks. So by default, there probably aren&#8217;t any News Articles in the database, so the Archive won&#8217;t be displaying anything. Let&#8217;s add some News, so we can see how it looks.</p>
252
+ <h5 id="adding-content-via-the-content-library">2.13.2 Adding content via the Content Library</h5>
253
+ <p>Choose the content library tab, and open the &#8216;News&#8217; module, by clicking the &#8216;News&#8217; link on the left. The &#8216;News Article&#8217; content type should be selected. Click the &#8216;Add New Content&#8217; to create a News Article. On the form, fill in a suitable name, summary, set the release date to today and body, and then click save.</p>
254
+ <p>Now return to the recently added portlet. You can do this by opening the &#8216;Core&#8217; module, selecting &#8216;portlets&#8217; and browsing/searching for the portlet you created. This will allow you do see the portlet in isolation from the page. Alternatively, you can return to the page you were on, to see the portlet where it is placed. The portlet should now be displaying a summarized version of the News Article you just created. You can control how the portlet displays the list by editing the template, which requires an understanding of Ruby/<span class="caps">ERB</span> and Html.</p>
255
+ </td>
256
+ </tr>
257
+ </table>
258
+ </div>
259
+ </div>
260
+ <br clear="all"/>
261
+ <div class="bottom_cap"></div>
262
+ </div>
263
+ </div>
264
+ </body>
265
+ </html>
266
+
data/lib/cms/behaviors/attaching.rb CHANGED
@@ -149,7 +149,7 @@ module Cms
149
149
  end
150
150
 
151
151
  def after_publish
152
- attachment.publish
152
+ attachment.publish if attachment
153
153
  end
154
154
 
155
155
  #Size in kilobytes