Ticket #4915 (new defect)

Opened 1 year ago

Last modified 1 year ago

get_alloptions() v. wp_load_alloptions()

Reported by: mdawaffe Assigned to: anonymous
Priority: normal Milestone: 2.9
Component: General Version:
Severity: normal Keywords:
Cc:

Description

These seem to be near duplicates. One has some filters, one has some caching.

It'd be a strange plugin that used either. Can we deprecate one or the other?

Also note get_alloptions_110().

Change History

09/06/07 06:33:52 changed by markjaquith

We have one plugin in the repository that is still using get_alloptions().

http://svn.wp-plugins.org/inscript/trunk/inscript.php

The methods that use it are doing manual manipulation of the options table, and thus would be incompatible with any WP install using an options cache... so it needs updating anyway.

I say we yank this for 2.4, and notify the author of InScript? so he can update his plugin to use the options API.

12/06/07 04:49:28 changed by DD32

Whats the consensus?

dump get_alloptions() as its not used?

Move to depreciated and return wp_load_alloptions()?