Custom Post Type UI Extended by WebDevStudios

darapati27

Member

May 4, 2022

76

28

18

• Jun 18, 2022

• #21

Tomz said:

Custom Post Type UI Extended v1.9.0

Click to expand...

Thank you, sir

 

Nghia Lele

New member

Jul 8, 2022

25

6

3

• Jul 29, 2022

• #22

Tomz said:

Custom Post Type UI Extended v1.9.0

Click to expand...

You are a champ @Tomz ! Thank you!

 

bendfrozien

Member

Oct 9, 2020

123

23

18

indonesia

idlinky.com

• Sep 11, 2022

• #23

it has new update, please update it @Tomz

 

Nury

Member

Oct 11, 2018

97

27

18

• Oct 2, 2022

• #24

thanks up

 

Bluecozza

Member

Apr 27, 2019

52

26

18

• Oct 10, 2022

• #25

any update on this? @Tomz

 

Zippa

Member

Apr 14, 2020

65

62

18

Russia>Moscow reg>science city Dubna

• Nov 13, 2022

• #26

Custom Post Type UI Extended v 1.7.0​

 

Attachments

• cptui-extended-1_7_0.zip

  1.7 MB · Views: 35

• 
• 

Reactions: Valentina, darapati27 and Karltoto

tanierlyons

Well-known member

Staff member

Administrative

Moderator

May 24, 2018

75,198

111,758

120

• Dec 18, 2022

• #27

Custom Post Type UI Extended v1.11.1

 

Attachments

• cptui-extended-1.11.1.zip

  1.6 MB · Views: 67

• 

Reactions: influence, mohamadhassaan, Karltoto and 2 others

mohamadhassaan

New member

Dec 21, 2022

1

1

1

• Dec 26, 2022

• #28

Tomz said:

Custom Post Type UI Extended v1.11.1

Click to expand...

There has been a critical error on this website. Please check your site admin email inbox for instructions.

Learn more about troubleshooting WordPress.

SORRY IT WORK FINE , I JUST NEEDED TO INSTALL THE 'CUSTOM POST TYPE UI' PLUGIN FIRST

 

Last edited: Dec 26, 2022

• 

Reactions: 2GUS

influence

Member

Feb 23, 2021

33

5

8

• Feb 13, 2023

• #29

Plz update

 

bobsmith

Busy in real life so uploads will be soon

Null Master

Trusted Uploader

May 4, 2022

2,976

2,942

113

UK

• Feb 13, 2023

• #30

Tomz said:

Custom Post Type UI Extended v1.11.1

Click to expand...

@Tomz
If you are going to update this, would it be better off giving it it's own resource thread, better than being in a request thread dated from 2018.