{"id":2296,"date":"2020-06-16T11:59:16","date_gmt":"2020-06-16T16:59:16","guid":{"rendered":"https:\/\/xlinesoft.com\/blog\/?p=2296"},"modified":"2020-06-16T11:59:16","modified_gmt":"2020-06-16T16:59:16","slug":"context-help-in-your-web-applications","status":"publish","type":"post","link":"https:\/\/xlinesoft.com\/blog\/2020\/06\/16\/context-help-in-your-web-applications\/","title":{"rendered":"Context help in your web applications"},"content":{"rendered":"

This article explains how you can implement context help in your PHPRunner or ASPRunner.NET application. Maybe you need to display some hints for users or a link to a more detailed page in the manual. If you ever checked PHPRunner or ASPRunner.NET live demo you probably noticed how it looks there:<\/p>\n

\"\"<\/a><\/p>\n

We, of course, do not want to add those messages manually to every page. Instead, we will store all those messages in the database and display the relevant message based on what page we currently on. <\/p>\n

1. Table to store messages<\/h4>\n

The following script is for MySQL:<\/p>\n

\r\nCREATE TABLE `messages` (\r\n  `id` int(11) NOT NULL,\r\n  `pageName` varchar(100) COLLATE utf8mb4_bin DEFAULT NULL,\r\n  `pageType` varchar(100) COLLATE utf8mb4_bin DEFAULT NULL,\r\n  `value` text COLLATE utf8mb4_bin NOT NULL,\r\n  `project` int(11) NOT NULL\r\n) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_bin;\r\n\r\nALTER TABLE `messages` ADD PRIMARY KEY (`id`);\r\nALTER TABLE `messages` MODIFY `id` int(11) NOT NULL AUTO_INCREMENT;\r\n<\/pre>\n
Here is how sample data in the messages<\/strong> table looks.<\/p>\n
\"\"<\/a><\/p>\n
2. AfterAppInit event.<\/h4>\n
\r\n$page = preg_replace('\/(\\\/|\\.php)\/i', '', substr($_SERVER[\"PHP_SELF\"], \r\n   strripos($_SERVER[\"PHP_SELF\"],\"\/\")) );\r\n$sym_pos = strripos($page,\"_\");\r\n$selectData[\"pageName\"] = $sym_pos?substr($page,0,$sym_pos):$page;\r\n$selectData[\"pageType\"] = $sym_pos?substr($page,$sym_pos+1):\"\";\r\n$selectData[\"project\"] = 1;\r\n$record = DB::Select(\"messages\", $selectData )->fetchAssoc();\r\n$_SESSION[\"messages\"] = \"\";\r\nif( $record ) $_SESSION[\"messages\"] = $record[\"value\"];\r\n<\/pre>\n
Here we parse the current page URL to find the table name and page type (“list”, “add” etc). We could have just stored the file name like “customers_list.php” but we’d like to use the same table for PHPRunner and ASPRunner.NET and ASPRunnerPro demos so we doing it this way. <\/p>\n
The project<\/strong> field is not required if you only have a single project. We have multiple live demos so the following tells that we are working with Liev Demo 1. <\/p>\n
\r\n$selectData[\"project\"] = 1;\r\n<\/pre>\n
Once the message is retrieved we store it in the session variable $_SESSION[“messages”]<\/strong> so we can later use it anywhere on the page. <\/p>\n
3. Displaying the message<\/h4>\n
The easiest option is just to display it in the header. This is what we do in those live demos. Another option is to display it from the code snippet. <\/p>\n
\r\n<?php \r\nprint $_SESSION[\"messages\"];\r\n?>\r\n<\/pre>\n
4. Sample message HTML code<\/h4>\n
Here is HTML of the hint that is seen on the screenshot. <\/p>\n
\r\n<DIV class=\"col-md-8 col-md-offset-2 alert alert-success info big-info\">\r\n<DIV class=\"col-md-6\">\r\n<ul>\r\n<li>Preview with products<\/li>\r\n<li>Columns grid layout on the List page<\/li>\r\n<\/ul>\r\n<\/DIV>\r\n<DIV class=\"col-md-6\">\r\n<ul>\r\n<li>Custom template - without search panel<\/li>\r\n<li>Highlighting search results<\/li>\r\n<\/ul>\r\n<\/DIV>\r\n<\/DIV>\r\n<\/pre>\n
You can do something else, i.e. display a link to the page in the manual. <\/p>\n
Enjoy!<\/p>\n","protected":false},"excerpt":{"rendered":"
This article explains how you can implement context help in your PHPRunner or ASPRunner.NET application. Maybe you need to display some hints for users or a link to a more detailed page in the manual. If you ever checked PHPRunner or ASPRunner.NET live demo you probably noticed how it looks there: We, of course, do not want to add those messages manually to every page. Instead, we will store all those messages in the database and display the relevant message based on what page we…<\/span>Continue Reading “Context help in your web applications”<\/span> →<\/span><\/a><\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[16,1],"tags":[],"_links":{"self":[{"href":"https:\/\/xlinesoft.com\/blog\/wp-json\/wp\/v2\/posts\/2296"}],"collection":[{"href":"https:\/\/xlinesoft.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/xlinesoft.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/xlinesoft.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/xlinesoft.com\/blog\/wp-json\/wp\/v2\/comments?post=2296"}],"version-history":[{"count":6,"href":"https:\/\/xlinesoft.com\/blog\/wp-json\/wp\/v2\/posts\/2296\/revisions"}],"predecessor-version":[{"id":2305,"href":"https:\/\/xlinesoft.com\/blog\/wp-json\/wp\/v2\/posts\/2296\/revisions\/2305"}],"wp:attachment":[{"href":"https:\/\/xlinesoft.com\/blog\/wp-json\/wp\/v2\/media?parent=2296"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/xlinesoft.com\/blog\/wp-json\/wp\/v2\/categories?post=2296"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/xlinesoft.com\/blog\/wp-json\/wp\/v2\/tags?post=2296"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}