Nadiamode

actually it automatic show in all post, page including all custom post type

try change theme back to default and see

I agree too, no document, no description for each type, less example, no graphical user interface (GUI)

I can see option lists in setting page but I dont know what it does (some type)
No example (I see only 1 example there)

I think this plugin is for developer or at least understand coding and can copy/paste or understand what these “hideKey , true, label, radio, mediaButton, filesize etc.” stand-for and how to use them

I use this plugin because

1. many people use it (Downloads: 243,469)
2. there’re suggest link from codex to here
3. this is very first custom field plugin
4. so I hope a developer will alway continue developing this plugin in a long term

But I will lost my patient that I have to pay my time for try understand some type, key in option list that I don’t know where I can find the explanation

If there’s a choice, I will use below plugin instead

https://www.ads-software.com/extend/plugins/advanced-custom-fields/

only one thing that i dont like advanced-custom-fields because they add one extra meta field
advanced-custom-fields plugin become popular now (Downloads: 88,211)

average download per day around 1,000 (and continue increasing) compare to this plugin around 500 (and continue decreasing) – you can check via stats tab
this stats tell which plugin people love to use

because advanced-custom-fields is super easy to use, easy to understand
you no need to learn or waste your time for just creating some custom field

finally advanced-custom-fields has GUI, no more coding, copy/paste

Thank you for updating plugin to version 0.7.3.1

I notice you replace line 156

$taxonomies = get_taxonomies(array("show_ui" => true),'objects');

with

$taxonomies = get_taxonomies(array("show_ui" => true, "_builtin" => false),'objects');

but permalink that use “type” as custom taxonomy still doesn’t work when activate plugin

http :// example. com/type/digital-sound/

i found that this function made something conflict with custom taxnomy = “type”

I try remove below code from plugin and it work, I can access https://example.com/type/digital-sound/

$taxonomies = get_taxonomies(array("show_ui" => true),'objects');
		foreach ( $taxonomies as $taxonomy => $objects ):
			$wp_rewrite->add_rewrite_tag("%$taxonomy%", '(.+?)',"$taxonomy=");
		endforeach;

use multiple option to do this

it work now, thank so much, actually i forgot to flush rewrite rule :p

another one issue is before 0.7.2.1 – it not append extra “slash”

but now it append “/” even i haven’t add it

example ver 0.7 – i use — > CPT/%post_id%
my url show — > CPT/2563

but ver 0.7.2.1 – i use — > CPT/%post_id%
my url show — > CPT/2563/

i need it too, i want to add image to each custom taxonomy term

hi, after i run a plugin with default settings for 2-3 days

i found that there re still DUPLICATE user in table WP_USERS in database

i have tick “Don’t cache queries for logged in users” in “Database Cache” already

now i have to put “users” in “Ignored query stems:” to prevent duplicate row problem

anybody use db cache and have problem same me? check your users table

sometime i also have problem with .htaccess file

old one is corrupt even inside code still same

i have to delete the old one and copy(or create new) working one from another site and change inside code later

* dont download old .htaccess (that show error) to local computer > edit > and upload again
** just delete and try make new .htaccess

—

for plugin
– change plugin folder name (to disable plugin)
– delete all caches file in cache folder

w3 total cache >
go to setting > browser cache

anyone know how plugin work?

how plugin rebuild cache file?

how plugin rebuild cache file when logged-in user visit that page?

Why homepage’s new cache file alway create?

Why some single post’s new cache file alway create?

1. try delete old .htaccess upload a new one

2. try change permalink back to ugly url ?p=103 to see it work or not

use ETAG in browser cache

browser will check if file has been modified via ETAG

very nice, now support all custom post types too

better to post via /links because facebook.com/twitter app does not tweet if that link come from /feed, it tweet (via fb app) only /links