It means that you have some url parameter loading from site, as reaction to some plugins, or file, or some changes, or behavior on site that may be loaded by some php code. In this scenario it can’t be exactly seen where is it coming from, but it looks like starting some type of increment. … Read more
I just examined your URL http://www.homecredit.ph/wp-content/uploads/home1/homecre1/public_html/files/News-26.jpg and code and noticed that, you are saving your image in http://www.homecredit.ph/files/News-26.jpg path but trying to access from upload directory of WordPress. /home1/homecre1/public_html/files/News-26.jpg – this is the path stored in database for your attachment ID. /home1/homecre1/public_html/ – This is your root directory where WordPress installed. So better save only … Read more
I ended up with this <?php //get children of page 241 and display with custom fields $args=array( ‘post_parent’ => 825, ‘post_type’ => ‘page’, ); $my_query = null; $my_query = new WP_Query($args); if( $my_query->have_posts() ) { while ($my_query->have_posts()) : $my_query->the_post(); ?> <?php $img = wp_get_attachment_image_src( get_post_meta($post->ID, ‘product_logo’, true)); ?> <?php $alt_text_for_logo = get_post_meta($post->ID, ‘alt_text_for_logo’, true); ?> … Read more
There are many reasons why WP could display this: 1 Insufficient file permissions on wp-admin folder (check this with ftp) 2 Prefix not consistently the same in database and wp-config (less likely in this case, but check anyway). 3 .htaccess doesn’t reroute wp-admin folder correctly 4 User roles not well defined in database (wp_capabilities should … Read more
The issue with your desired structure (and that categories without base are common request but commonly unreliable) is ambiguity. Each rewrite rule is like a tiny program, explaining WP how to turn URL into query variables. It is very important that WP can reliably distinguish which of the rules should handle particular URL. In plain … Read more
There is no way this kind of functionality exist without some plugin/code to implement it and without doing actual rewrites. WordPress core do not know what is a “stop word” and do not believe in multiple URL for the same content. If a theme was changed, this might have been a code in the theme … Read more
It works for me. add_filter(‘post_link’, ‘locale_permalink’, 10, 3); add_filter(‘post_type_link’, ‘locale_permalink’, 10, 3); function locale_permalink($permalink, $post_id, $leavename) { if (strpos($permalink, ‘%category_slider%’) === FALSE) return $permalink; $post = get_post($post_id); if (!$post) return $permalink; if ($post->post_type != ‘post’) { return $permalink; } else { $terms = wp_get_object_terms($post->ID, ‘category_slider’); if (!is_wp_error($terms) && !empty($terms) && is_object($terms[0])) $taxonomy_slug = $terms[0]->slug; else … Read more
The question isn’t very clear to me but i’ll attempt to answer anyway, forgive me if it’s obvious to you: What you describe is the behavior of “custom post types” When you create custom post types you define a slug like your “suburl” and “suburl2” and all posts created under that type fall under site.com/suburl/post-title … Read more
Now that you’ve made the custom taxonomy (and slug), you probably need to ‘reindex’ so to speak. Go to your WordPress Admin > Settings > Permalinks and make a change (make note of your original setting). Save, then change back to the original setting and save again. Your url new taxonomy should work then.
I combined this nice solution for adding an additional option to the permalinks page and this snippet for adding a custom base name to page permalinks. Usage Save the snippet below as wpse238124-page-base.php, place it in your plugins directory, and activate Page Base on your plugins page. Then, visit your permalinks page, enter your desired … Read more