Up to 50 percent off

Forum Replies Created

Viewing 15 Topics - 1 through 15 (of 24 total)
Author Posts
September 24, 2014 at 2:56 am in reply to: Create hyperlinked images 27342
John John This reply has been marked as private.
September 19, 2014 at 7:44 pm in reply to: Create hyperlinked images 27043
John John This reply has been marked as private.
September 3, 2014 at 10:48 pm in reply to: Create hyperlinked images 26270
John John This reply has been marked as private.
September 1, 2014 at 10:36 pm in reply to: Create hyperlinked images 26155
John John

OK, thank you.
Is this something I could hire one of the Frontend developers to do for me?

July 23, 2014 at 1:19 am in reply to: Two custom fields on the same line 23989
John John

I’m afraid this thread has gone full circle and you’ve given me the same answer Sk_Shaikat gave me at the start to a question I didn’t ask.

I am not trying to style the fields in the form. I can see that is easy.
I am trying to style the submitted content of those fields in the front end view.

Because these are all generated by the same bit of code in wpuf-functions.php, every submitted text field has the same class, so they cannot be individually styled.

July 22, 2014 at 3:58 am in reply to: Two custom fields on the same line 23904
John John

I don’t believe it is possible for a developer to do this without rewriting code in wpuf-functions.php.
As coded, there is no way to individually style the output of custom fields. Using nth-child pseudo-class, as you suggested, is the nearest, but for the reasons I gave, it is inadequate.

By adding classes to wpuf-functions.php, such as <li class="imagefield"> and <li class="textfield"> it is at least possible to separately style those elements. However, the custom text fields simply cannot be individually styled unless the number of fields submitted by the forms is forced to remain the same by making them all ‘Required’.

In my view this issue is not resolved because it’s a limitation inherent to Frontend Pro and should be addressed in a future release.

July 20, 2014 at 2:35 am in reply to: Prevent users from deleting images 23784
John John

Should anyone else wish to do this – I simply hid the delete button on the edit page with this:

/* hide Delete button on Edit Form */
.page-id-275 .attachment-delete {
   display: none !important;
}

(where page-id-[number] matches the page-id number of your edit form).
The same technique could of course be used for the submission page.

It would not prevent someone determined to delete the images, but serves my purpose.

July 19, 2014 at 8:34 pm in reply to: Preserve changed file after update 23780
John John

I’ve being trying to get this to work without success.
I have a modified wpuf-functions.php and render-form.php

I tried the following:

/themes/tewntytwelve-child/WPUF/WP-User_Frontend/class/render-form.php
/themes/tewntytwelve-child//WP-User_Frontend/class/render-form.php
/themes/tewntytwelve-child/WPUF/wp-user-frontend-pro/class/render-form.php
/themes/tewntytwelve-child/wp-user-frontend-pro/class/render-form.php

Maybe this only works for template files?

July 17, 2014 at 7:04 pm in reply to: Two custom fields on the same line 23726
John John

I’m sorry, I don’t understand. I did make the form first but I can’t see how to apply CSS to the content of the submitted fields because they don’t have unique classes and the :nth-child pseudo-class approach requires that I know how many fields will actually be submitted. This, as I said, will vary from one post to the next.

July 16, 2014 at 1:50 am in reply to: Prevent users from deleting images 23629
John John

Thanks for your reply. I will have to remove the delete button then.

July 16, 2014 at 1:44 am in reply to: Two custom fields on the same line 23628
John John

Thank you for the suggestion.

I tried:
.wpuf_customs li:nth-child(4n + 2), .wpuf_customs li:nth-child(4n + 3) {display:inline;}

Unfortunately this doesn’t work because I don’t know in advance how many fields will be submitted by the form. Some fields are not required and more than one image field can be submitted, for example.

July 12, 2014 at 5:43 pm in reply to: Two custom fields on the same line 23381
John John

Yes it possible to place the submitted content of two (or more) custom fields on the same line.

This topic is marked Resolved, but I don’t think this is correct.

Editting the style sheet of my theme would only work if Frontend User lets me apply unique classes to the submitted fields in the front end view.

All fields are <div class="entry-content"><ul class="wpuf_customs"><li> – so any CSS I use will affect them all.

July 7, 2014 at 7:00 pm in reply to: Duplicate Form not working 23126
John John

Thank you ndw!

July 7, 2014 at 6:39 pm in reply to: Updated to 2.2.2 All forms missing fields 23121
John John

I’m not sure if this is relevant, as it applies to the submitted content, not the forms themselves, but when I updated to version 2.2.2, the Custom Fields in post tick box (under User Frontend/SettingsGeneral Options tag) defaulted back to not show custom fields on post content area.

So I had to tick that box again to restore the missing content.

July 7, 2014 at 6:27 pm in reply to: Duplicate Form not working 23120
John John

This is marked as Resolved but I encounter the same issue with latest version 2.2.2.
Is there a fix?

Viewing 15 Topics - 1 through 15 (of 24 total)