Paolo

Thanks for letting us know 🙂

oh ok,

the lat and long problem is CSS. They are there, but text is white on a white field, so they look empty, but they are there.

You have the same problem on the login form.

The faulty CSS is here: http://meetupforcoffee.com/wp-content/uploads/custom_styles/dynamic.css?ver=4.1.4

.main-color, .main-color .logo a, .main-color .breadcrumb a, .main-color .nav-pills > li > a, .main-color .nav-pills > li.active > a, .main-color .nav-tabs > li > a, .main-color .kleo-tabs .nav-tabs li a i, .main-color .kleo-tabs .tabdrop .dropdown-menu li a, .main-color .wpb_tour .nav-tab li a, .main-color .sidebar ul li a, .main-color .sidebar .widget-title, .main-color .sidebar h4.widget-title a, .main-color .widget_tag_cloud a, .main-color #wp-calendar tbody td:hover, .main-color .btn-see-through:hover, .main-color article .article-meta .entry-date, .single-attachment .main-color .link-list a.post-time, .main-color input[type="text"], .main-color input[type="password"], .main-color input[type="date"], .main-color input[type="datetime"], .main-color input[type="datetime-local"], .main-color input[type="month"], .main-color input[type="week"], .main-color input[type="email"], .main-color input[type="number"], .main-color input[type="search"], .main-color input[type="tel"], .main-color input[type="time"], .main-color input[type="url"], .main-color textarea, .main-color #buddypress div.item-list-tabs a, .main-color #bp-login-widget-submit, .main-color .widget_bp_groups_widget .item-options a, .main-color .widget_bp_core_members_widget .item-options a, .main-color .widget_bp_core_friends_widget .item-options a, .main-color .widget_bp_groups_widget, .main-color .widget_bp_core_members_widget, .main-color .widget_bp_core_friends_widget, .main-color .bp-login-widget-user-logout a, .main-color .read-notifications td.notify-text a, .main-color #buddypress div.activity-comments form textarea, .main-color #buddypress div#item-nav ul li a:hover::before, .main-color #buddypress div#item-nav ul li.current a::before, .main-color #buddypress button, .main-color #buddypress a.button, .main-color #buddypress input[type="submit"], .main-color #buddypress input[type="button"], .main-color #buddypress input[type="reset"], .main-color #buddypress ul.button-nav li a, .main-color #buddypress div.generic-button a, .main-color.bp-full-width-profile div.generic-button a, .main-color #buddypress .portfolio-filter-tabs li a, .main-color .profile-cover-action a.button:hover, .main-color .profile-cover-action a.button::before, .main-color .bbp-pagination-links a:hover, .main-color .bbp-pagination-links span.current, .main-color #rtMedia-queue-list .remove-from-queue, .main-color .rtmedia-container .rtmedia-editor-main dl.tabs dd.active > a, .main-color .rtmedia-activity-container .rtmedia-editor-main dl.tabs dd.active > a, .main-color #buddypress div.rtmedia-activity-container .rtmedia-editor-main dl.tabs dd.active > a, .main-color .kleo-toggle-menu .minicart-buttons .btn-default {
    color: #ffffff;
}

Thanks

Hi,

I flagged this for the developers, I’m not 100% sure it is possible.

They’ll let you know asap.

Thanks

Hi,

did you try the code provided there?

hi,

there is a JS error :

TypeError: this.notes[0] is undefined
https://widgets.wp.com/notifications/build.min.js?6a0b66a8f2bf309ea22cb7a194121f6d
Line 10

Appears to be coming from a JetPack component. Can you please try to disable it momentarily to see if that is it?

Let us know,

Thanks

Hi,

sorry I missed to attached the image, but yes everything looks like it is working fine now.

Warnings are not errors, they are just notices and in your case the problem was just temporary.

Thanks

hi,

I’m not sure cPanel makes all folder within wp-content have the same permission recursively.

Please provide FTP credentials and we will have a look. Please ask read our support policy:

Support Forum – hours of operations

Our support hours are Monday to Friday, 09:00 to 18:00 (UK Time). We guarantee an answer within 24 hours to all Support Topic Monday to Friday and within 48 hours during weekends. This doesn’t mean all solutions will be provided within 24 or 48 hrs. For more advanced or technical queries it may as well take longer.

Hi,

the demo content supplied is supplied published with or without you creating the custom fields.

Please try to put a generic value in all of those fields, or make them non mandatory and you will see that the listings will get published.

After all, that is the logic behind mandatory fields.

Thanks