[solved]FC 2.0:Remove fcvote and fcfav css and js from code

gcprnet
Topic Author
Offline
Elite Member

12 years 2 months ago - 12 years 2 months ago #22465 by gcprnet

[solved]FC 2.0:Remove fcvote and fcfav css and js from code was created by gcprnet

I do not use the voting and the favourite functions in flexicontent so I disabled them in the backend at the fields page but the links to the .js and the .css still show up in the <head> section of my pages. Is there a way to get rid of the unneccessary scripts and css?
Regards

Last edit: 12 years 2 months ago by gcprnet.

Please Log in or Create an account to join the conversation.

ggppdk
Offline
Administrator

12 years 2 months ago #22472 by ggppdk

Replied by ggppdk on topic [solved]FC 2.0:Remove fcvote and fcfav css and js from code

Regardless of whether you display the fields or not, the css and js files will be added:
-- if the voting or favourites fields get created

Goto to FLEXIcontent global configuration and in performance parameters group set parameter:
"Always create field html" to the value:
"Only when needed" or to "Never unless in a template position"

Regards

-- Flexicontent is Free but involves a big effort on our part.
Like the our support? (for a bug-free FC, despite having a long list of functions) Like the features? Like the ongoing development and future commitment to FLEXIcontent?
-- Add your voice to the FLEXIcontent JED listing with a 5-star...

Please Log in or Create an account to join the conversation.

gcprnet
Topic Author
Offline
Elite Member

12 years 2 months ago #22478 by gcprnet

Replied by gcprnet on topic [solved]FC 2.0:Remove fcvote and fcfav css and js from code

It is set to only when needed...
Regards

Please Log in or Create an account to join the conversation.

ggppdk
Offline
Administrator

12 years 2 months ago #22482 by ggppdk

Replied by ggppdk on topic [solved]FC 2.0:Remove fcvote and fcfav css and js from code

Try setting it to "never unless in a template position"

This is because some templates may uses core fields without them being in a template position.

-- So for compatibility reasons all core fields are created in item view.

Regards

Please Log in or Create an account to join the conversation.