Title: Not hooked?
Last modified: August 22, 2016

---

# Not hooked?

 *  Resolved [bowoolley](https://wordpress.org/support/users/bowoolley/)
 * (@bowoolley)
 * [11 years, 4 months ago](https://wordpress.org/support/topic/not-hooked/)
 * Hi – I thought I’d give this a try, since none of the other title-hiding plugins
   seem to be up to date. However, it requires me to install the WP Autoloader plugin
   first. It would be good to mention that in the installation instructions; the“
   not hooked” message is a little off-putting.
 * Otherwise, it’s great – the ability to hide titles on custom post types is fabulous!
   I’ll rate it as soon as I’ve played with it a little more.
 * [https://wordpress.org/plugins/hide-singular-title/](https://wordpress.org/plugins/hide-singular-title/)

Viewing 2 replies - 1 through 2 (of 2 total)

 *  Plugin Author [WP Apps](https://wordpress.org/support/users/wp-apps/)
 * (@wp-apps)
 * [11 years, 4 months ago](https://wordpress.org/support/topic/not-hooked/#post-5627971)
 * Hi!
 * Thank you for comment. This plugin actually comes with built in documentation,
   which is very detailed. I’m sure that this kind documentation is rare for free
   plugins. This built in documentation covers several topics:
    - Installation
    - Settings
    - Post Settings
    - Quick Edit
    - Shortcodes
    - Support
 * [WP Autoloader](https://wordpress.org/support/topic/not-hooked/myminiapp.com/wordpress-plugins/wp-autoloader/?output_format=md)
   is an enterprise level but a free plugin, which autoloads PHP classes and provides
   an awesome framework for plugins development.
 * Hooking is a **standard procedure** for WordPress framework. Please read more
   about **action hooks** here: [WordPress Action Hooks](http://codex.wordpress.org/Plugin_API/Action_Reference).
 *  Plugin Author [WP Apps](https://wordpress.org/support/users/wp-apps/)
 * (@wp-apps)
 * [11 years, 4 months ago](https://wordpress.org/support/topic/not-hooked/#post-5627991)
 * **Just for clarity.** Hide Singular title is based on **component based software
   engineering**.
 * Component-based software engineering (CBSE) (also known as component-based development(
   CBD)) is a branch of software engineering that emphasizes the separation of concerns
   in respect of the wide-ranging functionality available throughout a given software
   system. It is a reuse-based approach to defining, implementing and composing 
   loosely coupled independent components into systems. This practice aims to bring
   about an equally wide-ranging degree of benefits in both the short-term and the
   long-term for the software itself and for organizations that sponsor such software.
 * Software engineering practitioners regard components as part of the starting 
   platform for service-orientation. Components play this role, for example, in 
   web services, and more recently, in service-oriented architectures (SOA), whereby
   a component is converted by the web service into a service and subsequently inherits
   further characteristics beyond that of an ordinary component.
 * Components can produce or consume events and can be used for event-driven architectures(
   EDA).
 * An individual software component is a software package, a web service, a web 
   resource, or a module that encapsulates a set of related functions (or data).
 * All system processes are placed into separate components so that all of the data
   and functions inside each component are semantically related (just as with the
   contents of classes). Because of this principle, it is often said that components
   are modular and cohesive.
 * With regard to system-wide co-ordination, components communicate with each other
   via interfaces. When a component offers services to the rest of the system, it
   adopts a provided interface that specifies the services that other components
   can utilize, and how they can do so. This interface can be seen as a signature
   of the component – the client does not need to know about the inner workings 
   of the component (implementation) in order to make use of it. This principle 
   results in components referred to as encapsulated. The UML illustrations within
   this article represent provided interfaces by a lollipop-symbol attached to the
   outer edge of the component.
 * However, when a component needs to use another component in order to function,
   it adopts a used interface that specifies the services that it needs.
 * Another important attribute of components is that they are substitutable, so 
   that a component can replace another (at design time or run-time), if the successor
   component meets the requirements of the initial component (expressed via the 
   interfaces). Consequently, components can be replaced with either an updated 
   version or an alternative without breaking the system in which the component 
   operates.
 * As a general rule of thumb for engineers substituting components, component B
   can immediately replace component A, if component B provides at least what component
   A provided and uses no more than what component A used.
 * Software components often take the form of objects (not classes) or collections
   of objects (from object-oriented programming), in some binary or textual form,
   adhering to some interface description language (IDL) so that the component may
   exist autonomously from other components in a computer.
 * When a component is to be accessed or shared across execution contexts or network
   links, techniques such as serialization or marshalling are often employed to 
   deliver the component to its destination.
 * Reusability is an important characteristic of a high-quality software component.
   Programmers should design and implement software components in such a way that
   many different programs can reuse them. Furthermore, component-based usability
   testing should be considered when software components directly interact with 
   users.
 * It takes significant effort and awareness to write a software component that 
   is effectively reusable.

Viewing 2 replies - 1 through 2 (of 2 total)

The topic ‘Not hooked?’ is closed to new replies.

 * ![](https://s.w.org/plugins/geopattern-icon/hide-singular-title_b39382.svg)
 * [Hide Singular Title](https://wordpress.org/plugins/hide-singular-title/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/hide-singular-title/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/hide-singular-title/)
 * [Active Topics](https://wordpress.org/support/plugin/hide-singular-title/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/hide-singular-title/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/hide-singular-title/reviews/)

 * 2 replies
 * 2 participants
 * Last reply from: [WP Apps](https://wordpress.org/support/users/wp-apps/)
 * Last activity: [11 years, 4 months ago](https://wordpress.org/support/topic/not-hooked/#post-5627991)
 * Status: resolved