
Java Man |

From the description of hybrid classes in the ACG the definition of parent classes:
Parent Classes:
Each of the following classes draws upon two classes to form the basis of its theme. While a character can multiclass with these parent classes, doing so usually results in redundant abilities. Such abilities don't stack unless specified. If a class feature allows the character to make a one-time choice (such as a bloodline), that choice must match similar choices made by the parent classes and vice-versa (such as selecting the same bloodline).
No where does ir say a Brawler is a fighter or monk, or counts as such. Some hybrid classes contain specific verbage to count as one of the parent classes for feat choices or something. Since a Brawler is not a fighter, it cannot take a fighter archetype, even if it seems to have the proper class features to trade out.
I use brawler as an example only, his applies to all ACG classes.
I cannot find any more specific rule for you if this is not clear enough. You say there are multiple opinions, I say there is a correct statement, and incorrect ones.

Kazaan |
The hybrid classes were originally planned with the concept of being an alternate class of both parents in mind, but that idea was dropped in development. If they had kept that idea, then the hybrid classes would not be able to multi-class with either parent class and they would be eligible for archetypes of either parent class provided they had all the class features to trade out. However, that's all moot since the hybrid classes count just as any other base class.

Drahliana Moonrunner |

I know there have been several conversations about this topic, and everyone seems to have their own opinions.
Can someone provide the source of where it says that if a Hybrid class meets all the requirements, it can/can't take an archetype of the parent class?
No one will because that's not how Paizo makes rules.
The burden of proof is to find the rules to say that it CAN. A warpriest is not a cleric, nor it is a fighter, it is a completely separate class that draws on design elements for both, but remains distinct from either.

jbadams |
Agreed with the above -- there are no (valid) conflicting opinions on this -- by the rules a hybrid class is a separate class that does not count as either of it's parent classes and is therefore not eligible to take archetypes of the parent classes.
That is, a hybrid class NEVER qualifies for parent class archetypes by failing the very first requirement of not being the class in question.
.
.
That being said, allowing this as a house rule in your home games may not be too game-breaking, but discussions of house rules don't belong in the rules forum. If they decided to allow it most GMs would likely require you to have ALL class features that are normally traded out.

GinoA |

That being said, allowing this as a house rule in your home games may not be too game-breaking, but discussions of house rules don't belong in the rules forum. If they decided to allow it most GMs would likely require you to have ALL class features that are normally traded out.
I'd suggest adding the can't multi-class with either base-class rule as well.