CSS problem between FC and googlemaps (mike reumer)

More
11 years 2 weeks ago #41313 by rottenberg
Of course,
I have got from Mike Reumer the beginning of a solution, but it's not optimal.

I'm waiting his answer and I send to copy on the forum.

best regards

Michel

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

More
11 years 1 week ago #41316 by rottenberg
I have received the solution from Mike Reumer :

Thank you for the answer of the developer of Flexicontent.

It is not the html that adds a label entity after a checkbox or radio input, but has to be done by the logic so my plugin.
The label entity has new features since HTML5 and not in previous versions so it was not necessary to add it.
I will put it on the list of changes to add labels on the titles of input fields. I will inform you when it is done and send you a new version.

The suggestion to add label will not solve the problem, because the css of flexicontent will still style the object and it will show a radiocontrol that does not work. So the developer should set his css styling only for his extension as he mentioned too.

For the short term, I advice to add the following css to your template css or to the map css parameter at the configuration of the plugin:
.map input[type=radio ]:not(old) {
opacity : 1 !important;
display: inline-block !important;
}


What I did to solve the problem :

For each article able to use a google map, I have created fields to enter the different parameters used in the {mosmap...} plugin.

I have also created a field which copy all parameters needed to create the map. a '|' separates each parameter. In the prefix of the this variable I give [plan] and [/plan] in the suffix.

I get this data [plan]param_1|param_2|....|parma_n[/plan]

I use REREPLACER plugin (nonumber) to transform the [plan]...[/plan] in a mosmap plugin which will be displayed in the site.
This is done with a PHP script.

To solve the current problem I have just added the following HTML before the php script :

<style type="text/css">
.map input[type=radio ]:not(old) {
opacity : 1 !important;
display: inline-block !important;
</style>



best regards

Michel

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

More
11 years 1 week ago #41318 by ggppdk
Hello

i will see to exclude this CSS for all frontend views, except for item form,

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.

More
11 years 1 week ago #41323 by rottenberg
thank you very much.

best regards

Michel

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

Moderators: vistamediajoomlacornerggppdk
Time to create page: 0.296 seconds
Save
Cookies user preferences
We use cookies to ensure you to get the best experience on our website. If you decline the use of cookies, this website may not function as expected.
Accept all
Decline all
Essential
These cookies are needed to make the website work correctly. You can not disable them.
Display
Accept
Analytics
Tools used to analyze the data to measure the effectiveness of a website and to understand how it works.
Google Analytics
Accept
Decline