Dapper query result returns DapperRow collections: IEnumerable<dynamic>{List<Dapper.SqlMapper.DapperRow>}. In order to use the data inside DapperRow object, we need to convert the data into usable types. Get single value var data = conn.ExecuteScalar("select top 1 title from book"); string title = $"{data}"; int id = conn.ExecuteScalar<int>("select top 1 id from book"); Get data from a single row var row = conn.QuerySingle("select top 1 title, url_target from book"); var title = $"{row.title}"; Get data as a Array: var data = conn.Query("select title, url from book").Select(x => x.title).ToArray(); foreach(var d in data){ string title = d; } Get data as a List: var data = conn.Query("select title, url from book").Select(x => x.title).ToList(); foreach(var d in data){ string title = d; } Get data as a Dictionary: var data = conn.Query("select title, url from book").ToDictionary(row => (string)row.title, row => (string)row.url); foreach(var k in data.Keys){ string key = k; string value = data[k]; } Get data as an object: var books = conn.Query<Book>("select * from book"); //returns IEnumerable<Book> foreach(var book in books){ string title = book.Title; } Dapper automatically mapped the column data to the fields in the object by their names. 610 total views, 5 views today
Nowadays more and more web crawlers visit a website, some are good for you, such as google search engine, they respect robots.txt protocol. But some of them have bad behavior that has negatively impact to your site. How to block the bad bots These crawlers are called bot. A bot is a software program that operates on the Internet and performs repetitive tasks. While some bot traffic is from good bots, bad bots can have a huge negative impact on a website or application. So we want to block those bad bots from visiting our site. Normally, we can set rule in robots.txt file, but the bad bots do not respect these rules. So setting up robots.txt file is only for good bots. To be sure the bad bots are blocked, we have to use .htaccess file. Here are the steps: 1. find out the bot keyword from the user-agent from the log. 2. add the following script to the top of .htaccess file: a) set rewrite condition: It uses regular expression to match multiple user agents in one line. RewriteEngine On RewriteCond %{HTTP_USER_AGENT} "dataforseobot|Yandex|AhrefsBot|BLEXBot|SemrushBot" [NC] RewriteRule "^.*$" - [F,L] Or b) using SetEnvIf directives: SetEnvIfNoCase User-Agent "AhrefsBot" badbots SetEnvIfNoCase User-Agent "BLEXBot" badbots SetEnvIfNoCase User-Agent "SemrushBot" badbots SetEnvIfNoCase User-Agent "YandexBot" badbots SetEnvIfNoCase User-Agent "dataforseobot" badbots <Limit GET POST HEAD> Order Allow,Deny Deny from env=badbots </Limit> Both scripts are equiverant, just pick the one you like. By using the script above the page will return 403 (forbidden) to the bad bots. Test the effects Here's an example that uses chrome browser…
AlT attribute for an image is helpful factor for SEO. But the plugin "Social Media Share Buttons" by Sygnoos is not adding alt attribute for all social images. The following is my approach to add alt attribute to the social images. For this reason, Bing search console is always give a warning message and refuse to index the site. 1. Find possible keyword using browser tool. 2. locate keyword using Visual Studio find feature. Location: /wp-content/plugins/social-media-builder/js/addNewSection/SGMBWidget.js 3. add alt attribute to the images with jQuery. 4. result: Additionary, to set all images ALT value where alt is missing, using this script: Set alt value to image file name where alt is missing $('img').each(function(i,e){ if($(e).attr('alt')=='') $(e).attr('alt', $(e).attr('src').replace(/^.*(\\|\/|\:)/, '').replace(/\.[^/.]+$/,'')); }); How to get this script? Explained below. //show all img src $('img').each(function(i,e){console.log($(e).attr('src'));}); //show all img alt $('img').each(function(i,e){console.log($(e).attr('alt'));}); //get file name from path filepath.replace(/^.*(\\|\/|\:)/, ''); //get file name without extension from file name filename.replace(/\.[^/.]+$/,''); //show all img file name without extension $('img').each(function(i,e){console.log($(e).attr('src').replace(/^.*(\\|\/|\:)/, '').replace(/\.[^/.]+$/,''));}); //set alt value to image file name where alt is missing $('img').each(function(i,e){if($(e).attr('alt')=='') $(e).attr('alt', $(e).attr('src').replace(/^.*(\\|\/|\:)/, '').replace(/\.[^/.]+$/,''));}); 1,002 total views, 3 views today
Background Info Theme: OceanWP Plugin: The Event Calendar Solution Event Calendar title in header bar is renderred by theme OceanWP in file: /themes/oceanwp/partials/function oceanwp_title(). The title is get by function oceanwp_title() in file: /themes/oceanwp/inc/helpers.php. In order to override the tile, we created a new file functions-events.php with the following code: if ( ! function_exists( 'oceanwp_title' ) ) { function oceanwp_title() { ... //copy code here from theme and insert the following code if( tribe_is_month() && !is_tax() ) { // Month View Page $title = esc_html__( 'Metro\'s Event Schedule', 'oceanwp' ); } elseif( tribe_is_month() && is_tax() ) { // Month View Category Page //echo 'Metros Event Schedule category page'; } // Last check if title is empty $title = $title ? $title : get_the_title(); // Apply filters and return title return apply_filters( 'ocean_title', $title ); } } In functions.php add include file statement: require_once('functions-events.php' ); Note: Translate Wrap string with function esc_html__() in order to retrieve the translation of the new string. Translate with Loco plugin. First the pot file need to be updated. Make sure the new string is shown in the file. Edit translate file, use Sync button to update the content strings. Result 1,835 total views, 5 views today
Emojis 😀 😀 😁 😁 😂 😂 😃 😃 😄 😄 😅 😅 😆 😆 😇 😇 😈 😈 😉 😉 😊 😊 😋 😋 😌 😌 😍 😍 😎 😎 😏 😏 😐 😐 😑 😑 😒 😒 😓 😓 😔 😔 😕 😕 😖 😖 😗 😗 😘 😘 😙 😙 😚 😚 😛 😛 😜 😜 😝 😝 😞 😞 😟 😟 😠 😠 😡 😡 😢 😢 😣 😣 😤 😤 😥 😥 😦 😦 😧 😧 😨 😨 😩 😩 😪 😪 😫 😫 😬 😬 😭 😭 😮 😮 😯 😯 😰 😰 😱 😱 😲 😲 😳 😳 😴 😴 😵 😵 😶 😶 😷 😷 😸 😸 😹 😹 😺 😺 😻 😻 😼 😼 😽 😽 😾 😾 😿 😿 🙀 🙀 🙁 🙁 🙂 🙂 🙃 🙃 🙄 🙄 🙅 🙅 🙆 🙆 🙇 🙇 🙈 🙈 🙉 🙉 🙊 🙊 🙋 🙋 🙌 🙌 🙍 🙍 🙎 🙎 🙏 🙏 🤐 🤐 🤑 🤑 🤒 🤒 🤓 🤓 🤔 🤔 🤕 🤕 🤖 🤖 🤗 🤗 🤞 🤞 🤟 🤟 🤠 🤠 🤡 🤡 🤢 🤢 🤣 🤣 🤤 🤤 🤥 🤥 🤦 🤦 🤧 🤧 🤨 🤨 🤩 🤩 🤪 🤪 🤫 🤫 🤬 🤬 🤭 🤭 🤮 🤮 🤯 🤯 🤰 🤰 🤱 🤱 🤲 🤲 🤳 🤳 🤴 🤴 🤵 🤵 🤶 🤶 🤷 🤷 🤸 🤸 🤹 🤹 🤺 🤺 🤼 🤼 🤽 🤽 🤾 🤾 🥂 🥂 🧐 🧐 🧑 🧑 🧒 🧒 🧓 🧓 🧔 🧔 🧕 🧕 🧖 🧖 🧗 🧗 🧘…
Usage To express: yóu, type the HTML entity like: yóu. Chinese PinYin（a e i o u） ā ā á á ǎ ǎ à à ē ē é é ě ě è è ī ī í í ǐ ǐ ì ì ō ō ó ó ǒ ǒ ò ò ū ū ú ú ǔ ǔ ù ù ǖ ǖ ǘ ǘ ǚ ǚ ǜ ǜ Greek characters Α Α Α Β Β Β Γ Γ Γ Δ Δ Δ Ε Ε Ε Ζ Ζ Ζ Η Η Η Θ Θ Θ Ι Ι Ι Κ Κ Κ Λ Λ Λ Μ Μ Μ Ν Ν Ν Ξ Ξ Ξ Ο Ο Ο Π Π Π Ρ Ρ Ρ Σ Σ Σ Τ Τ Τ Υ Υ Υ Φ Φ Φ Χ Χ Χ Ψ Ψ Ψ Ω Ω Ω α α α β β β γ γ γ δ δ δ ε ε ε ζ ζ ζ η η η θ θ θ ι ι ι κ κ κ λ λ Λ μ μ μ ν ν Ν ξ ξ ξ ο ο ο π π π ρ ρ ρ ς ς ς σ σ σ τ τ τ υ υ υ φ φ φ χ χ χ ψ ψ ψ ω ω ω ϑ ϑ ϑ ϒ ϒ ϒ ϖ ϖ ϖ Currency Symbols ¢ ¢ ¢ £ £ £ ¤ ¤ ¥ ¥ ¥ € € € ₠ ₠ ₰ ₰ ₳ ₳ Math Symbols ° ° ° ¹ ¹ ² ² ³ ³ < < < ≤ ≤…
This is a note for fixing Kratos theme multi-language issue. Basic information Theme: Kratos Language plugins: Polylang, Loco Language settings: en_CA, zh_CN Symptom On English version, always display Chinese words. While OceanWP theme displays correctly for multi-languages. Reason The theme offers multi-language support for American English, Japanese, and Chinese language files: en_US, ja_JP, zh_TW. For English only contains en_US, not en_CA. For multi-language use, I created a en_CA language file under common location: /wp-content/languages/themes/kratos-en_CA.po. In the theme, the language file location is locked on theme directory. Therefore all other languages that located on other location cannot be found. function theme_languages() { load_theme_textdomain('kratos', get_template_directory() . '/languages'); } add_action('after_setup_theme', 'theme_languages'); Fixing multi-language issue As a quick fix, just change en_CA to en_US, instead of creating another language file. Then it displays as expected. For better solution, the en_CA language file could be copied over to theme language directory, in order to keep Canadian English style. 1,873 total views
Category list on sidebar widget will display all categories on post category hierarchy by default. However, we do not want to display all of them for some reason. Here is simple technique to achieve this goal. Find category IDs First thing to do is to find out all category IDs that we don't want them to show on the sidebar. Run the following script against WordPress MySQL database. SELECT t.term_id catID,t.name FROM wp_terms t join wp_term_taxonomy tax on tax.term_id=t.term_id where tax.taxonomy='category' Snippets //Hide categories from WordPress category widget function exclude_widget_categories($args){ $exclude = "4,6,7,8,9,10,13,14,15,16"; $args["exclude"] = $exclude; return $args; } add_filter("widget_categories_args","exclude_widget_categories"); Apply the snippets There are many ways to apply the snippets. You could add it to theme functions.php file or using snippets plugin to apply the snippets code. In my case, I'm using snippets to apply the code. This way is better organized for reusing the snippets. Last words, This is the simplest way to contorl the category list on sidebar, but you may use other ways to control the category list on sidebar, for instance, find a proper plugin or write your own plugin to achieve it. 9,490 total views, 3 views today
WordPress Links Manager is a tool to manage a set of links. You can add, modify, and remove a link easily from admin dashboard. By default, WordPress come with a widget to add a sidebar, where the links will be shown. The Links Manager is provided by default in earlier versions of WordPress than Version 3.5. However, the WordPress Links Manager and blogroll are hidden for new installs. Moreover, if you used an earlier version than 3.5 and upgraded your installation, then the Links Manager was removed if you don’t have any links. Restoring the Links Manager 1. Using filter Add the following line to your theme’s functions.php file to enable WordPress Links Manager if you are using WordPress version 3.5 or higher To enable Links Manager in version 3.5+, just add the following code to one of the following locations: functions.php file of the theme; php snippets plugin; your own plugin; add_filter( 'pre_option_link_manager_enabled', '__return_true' ); Once enabled, you can see a Links tag in the left panel of the dashboard. 2. Change option value from database If you can access the database you could enable it pritty easy by changing the option value in the database directly. There is an option_name = 'link_manager_enabled' in wp_options table. You can set this value to 1 directly. update wp_options set option_value=1 where option_name='link_manager_enabled'; What Link Manager plugin does is just to change this value in wp_option table behind the scene using filter function. Displaying Links in sidebar WordPress provides a widget within its Links Manager. So you can easily locate links in the sidebar…
There are many things have to be done on background, for instance, version check, update theme, delete posts, delayed posting, delete transients, etc. In WordPress this background job is performed by WP-Cron, witch is defined in wp-cron.php file. WordPress cron is the system built-in process that handles the scheduling of time-based tasks. Out-of-the-box, WordPress performs a number of scheduled tasks, they include: WordPress core update checks Plugin update checks Theme update checks Publishing of scheduled posts WP-Cron takes its name from cron, which is a time-based job scheduler in Unix-like systems. However, WP-Cron is designed to work on any hosting provider (including shared hosting) without using any external software or tools for scheduling events. Problem of WP-Cron The wp-cron.php is triggered on every http request. If any scheduled event is due, the event is spawned to wp-cron.php for processing, so the event is triggered to run. This is unreliable, espectially for low traffic sites, or heavily cached sites, cause scheduled events to be missed if no traffic is received for a prolonged period of time. For high-traffic sites, WP-Cron is extremely inefficient. This is because WP-Cron will check for scheduled events on every page load. This could mean that the cron schedules are being checked multiple times per second. This is unnecessary and highly redundant, as scheduled events typically run in minutes or hourly, even monthly interval. Even wp-cron.php creates a lock in WordPress transient, witch stored in wp_options table, but for high traffice sites the high concurrent requests may still spawn multiple requests to wp-cron.php, thus increasing server load.…
