You can do this in 2 ways: Remove it from HTML source code (harder, but more correct) Find <footer class=”post-meta”> in your theme files, and remove (or comment) it (with contents). You will see something like this in one of your files: <footer class=”post-meta”> … <a href=”https://wordpress.stackexchange.com/questions/105324/…</a> … </footer> Just remove this part of code … Read more
You’d need to create the top-level menu page, and then the sub-menu after that. Here’s an example: function my_menu() { add_menu_page ( ‘MVC Events’, // $page_title ‘MVC Events’, // $menu_title ‘manage_options’, // $capability ‘mvc-events’, // $menu_slug ‘mvc-options’ // $function ); add_submenu_page ( ‘mvc-events’, // $parent_slug ‘ATB Event Options’, // $page_title ‘ATB Event Options’, // $menu_title … Read more
A simple approach would be a solution with CSS and PHP. <?php $postcount = 1; $wp_query = new WP_Query(); while ($wp_query->have_posts()) : $wp_query->the_post(); ?> <div class=”post-<?php echo $postcount ?>”> <h3><a href=”https://wordpress.stackexchange.com/questions/111019/<?php the_permalink() ?>” title=”<?php the_title(); ?>”><?php the_title(); ?></a></h3> <div class=”entry”> <?php the_excerpt(); ?> </div> </div> <?php $postcount++; endwhile; ?> Then you can style your website, … Read more
Have you seen the update_user_meta() WordPress function?
You aren’t returning data from the sanitize function: function kns_sanitize_options( $input ) { $input[‘option1’] = sanitize_text_field( $input[‘option1’] ); $input[‘option2’] = sanitize_text_field( $input[‘option2’] ); } There is therefore nothing to save. Try: function kns_sanitize_options( $input ) { $input[‘option1’] = sanitize_text_field( $input[‘option1’] ); $input[‘option2’] = sanitize_text_field( $input[‘option2′] ); return $input; } Secondly, you’ve registered the name of … Read more
If you’d dumped one of your $players you’d have seen the issue: object(WP_User)#126 (7) { [“data”]=> object(stdClass)#129 (10) { [“ID”]=> string(1) “9” [“user_login”]=> string(3) “abc” [“user_pass”]=> string(34) “$P$BmwzlhY1xP6JTBlbWzLPetkx8lB.Zo/” [“user_nicename”]=> string(3) “abc” [“user_email”]=> string(19) “[email protected]” [“user_url”]=> string(0) “” [“user_registered”]=> string(19) “2013-10-04 09:22:08” [“user_activation_key”]=> string(0) “” [“user_status”]=> string(1) “0” [“display_name”]=> string(3) “abc” } [“ID”]=> int(9) // removed … Read more
get_option() returns a string, it doesn’t print anything. You have to use echo or print. But you should use home_url() instead, because this takes care of the proper scheme (http or https): echo esc_url( home_url() ); Or, in case of the log in URL: echo esc_url( wp_login_url() );
Ok, So I have found a solution to my problem; Pagelines encodes each key and value pair into a json string, within in its own option called pl_settings in the wp_options table. They also give you access to each of these key->value pairs using the following: $value = pl_setting(‘option_key’) Thus I have taken the approach … Read more
It is pretty hard to tell since you didnt give a lot of information, but First, make sure both sites connect to the same database. Then add those lines in the wp-config.php of each sites to make sure your sites are going to get the right value of wp_home and wp_siteurl depending on which server … Read more
The solution was to change the permalink structure from /%postname%/%post_id% to: /%post_id%/%postname%/ This magically fixed it – possibly WordPress queries are not so efficient the other way around or I ran into a bug with a plugin. Anyway, it’s blazing fast again, both backend and frontend