vb.org Archive

vb.org Archive (https://vborg.vbsupport.ru/index.php)
-   vBulletin 4.x Add-ons (https://vborg.vbsupport.ru/forumdisplay.php?f=245)
-   -   New Posting Features - Easy Forms v4.x - Create a form or multiple forms without php or html knowledge (https://vborg.vbsupport.ru/showthread.php?t=234385)

thunderclap82 10-17-2011 02:28 AM

I have attachments enabled and just upgraded to 4.3. Now suddenly I no longer have the Manage Attachments button showing. Instead its just ().

Any ideas how to fix this?

midnz 10-17-2011 07:38 AM

Quote:

Originally Posted by jimmycongo (Post 2257203)
I have a myriad of forms set up on my boards, would installing the newest version wipe out those forms? If so, how can I go about saving them before updating?

On your misc.php?do=forms page you should see links to export your forms for safekeeping.

Edit Form Delete Form Copy Form Export Form Form Results Form Results Table Form Results Poll Export Form Results to Excel

bigrover 10-20-2011 04:48 PM

First, I gotta say this is my favorite mod. The help I received in this forum to do some posting to current forums and such was phenomenal. Thank you.

I am working on an upgrade for our current site which is running vB 4.1.2 PL2 and Easy Forms 4.2.5 and am testing it all out on another server. I've installed vB 4.1.7 and Easy Forms 4.3.0, then imported the forms from my main site.

First issue -- I use the custom form output with the following info on my current site:

PHP Code:

[B]{qn_restaurant}: [SIZE=4]{qo_restaurant}[/SIZE][/B]
[
B]{qn_date}: [/B]{qo_date}
[
B]{qn_contact}: [/B]{qo_contact}
[
B]{qn_phone}: [/B]{qo_phone}
[
B]{qn_email}: [/B]{qo_email}
[
B]{qn_url}: [/B]{qo_url}
[
B]{qn_city}, {qn_state}: [/B]{qo_city}, {qo_state}
[
B]{qn_location}: [/B]{qo_location}
[
B]{qn_recommend} [/B]{qo_recommend}

[
B]{qn_comments}: [/B]
{
qo_comments}

<
vb:if condition="$q[24]!=''">[HIDE]{qo_private}[/HIDE]</vb:if> 

It works perfectly on my main site, but on the test site with the new versions, some of the questions and answers are not properly referenced if I don't use the question number instead of the reference name. Nothing I can't deal with, but it might bite others who migrate over as well.

Second issue -- The other odd issue is on several occasions during testing the browser (firefox) popped up and warned me about leaving the page when I click either the submit or preview button. It doesn't occur every time, but I haven't pinned this issue down yet.

bigrover 10-20-2011 05:48 PM

A bit more followup...

I modified the output styling to use the question numbers rather than the reference name and that isn't working correctly either.

PHP Code:

[B]{qn_29}: [SIZE=4]{qo_29}[/SIZE][/B]
[
B]{qn_31}: [/B]{qo_31}
[
B]{qn_33}: [/B]{qo_33}
[
B]{qn_34}: [/B]{qo_34}
[
B]{qn_35}: [/B]{qo_35}
[
B]{qn_36}, {qn_37}: [/B]{qo_36}, {qo_37}
[
B]{qn_38}: [/B]{qo_38}
[
B]{qn_50} [/B]{qo_50}

[
B]{qn_52}: [/B]
{
qo_52}

<
vb:if condition="$q[54]!=''">[HIDE]{qo_54}[/HIDE]</vb:if> 

The ouput places the answer to question 54 where answer 52 should be. It does not display the answer to 54. The output is shown below. The public comments question indicates it is question #52. The answer that was submitted was "just here for the view" but you can see it duplicated the result from answer 54. It looks like there are some pointer issues somewhere. I may uninstall version 4.3.0 and try 4.2.5 on vB 4.1.7 and see what happens.

Form output:
Tops
Restaurant Name: Bottom's Up
Date of Visit: right now!
Phone Number:
Email Address:
Website, or Ad:
City, State: sa, mid
Location:
Would you recommend this Restaurant? yes

Public comments:
Why isn't this fo everyone?

answer 54:
Why isn't this fo everyone?

bigrover 10-20-2011 07:16 PM

Downgrading to version 4.2.5 did not help, and in some ways made matters worse. When it imported the forms that had been modified by version 4.3.0 the question #'s all changes, as did the form id #. All of the custom formatting based on question #'s were now incorrect.

Also, the form displayed properly when selected from the forms menu, but when called through my hooks, the vBulletin editor fields are really messed up.

I'm removing 4.2.5 and going back to 4.3.0 since it knows about the CKEditor. Then I'm going to build a test form from scratch and see if my problems are coming from the export/import process.

djbaxter 10-20-2011 08:30 PM

Quote:

Originally Posted by bigrover (Post 2259427)
Second issue -- The other odd issue is on several occasions during testing the browser (firefox) popped up and warned me about leaving the page when I click either the submit or preview button. It doesn't occur every time, but I haven't pinned this issue down yet.

This is an issue with vBulletin 4.1.6 and 4.1.7, either "by design" or "a bug" depending on who you talk to. It's annoying but nothing to do with this or any other add-on.

bigrover 10-20-2011 08:33 PM

It appears my problems are related to the use of more than on vB editor field on a form. My forms have two editor fields. If I import a form created in an older version of Easy Forms, I can access both of them, but only the data from the second one is returned regardless of which method I use to access the answer. If I build a new form from scratch and add two editor field questions, the first one does not work. Specifically, most of the buttons in the editor are greyed out, and the text area will not receive the focus to text can be entered. The second editor field works as expected.

Can we no longer have more than one editor field in a form?

I'm still getting the prompt about leaving the page when I try and submit a form, regardless of whether I use Firefox or IE as the browser.

djbaxter 10-20-2011 08:45 PM

Quote:

Originally Posted by bigrover (Post 2259533)
It appears my problems are related to the use of more than on vB editor field on a form. My forms have two editor fields. If I import a form created in an older version of Easy Forms, I can access both of them, but only the data from the second one is returned regardless of which method I use to access the answer. If I build a new form from scratch and add two editor field questions, the first one does not work. Specifically, most of the buttons in the editor are greyed out, and the text area will not receive the focus to text can be entered. The second editor field works as expected.

Can we no longer have more than one editor field in a form?

I'm still getting the prompt about leaving the page when I try and submit a form, regardless of whether I use Firefox or IE as the browser.

No, unfortunately. What I had to do was convert them to multiline text fields.

bigrover 10-20-2011 09:22 PM

Quote:

Originally Posted by djbaxter (Post 2259529)
This is an issue with vBulletin 4.1.6 and 4.1.7, either "by design" or "a bug" depending on who you talk to. It's annoying but nothing to do with this or any other add-on.

Yeah, uh that's a bug and I really don't care what the programmers say. That message is intended to indicate to users that they may be accidentally leaving a site where they have entered data but not processed it. Sad to see that cropping up in this new version.

The deeper I get into an upgrade to 4.1.7, the less I am pleased with it. My production site has been compromised and I am constantly fighting spammers using it. The hosts we have used blame it on vB 4.1.2 PL2 and all want me on the latest version. So nice how they screwed up so much that most of my mods no longer function correctly.

Sorry, just venting. In programming, like medicine, the first rule should be "do no harm".

bigrover 10-20-2011 09:26 PM

Quote:

Originally Posted by djbaxter (Post 2259538)
No, unfortunately. What I had to do was convert them to multiline text fields.

I was worried that would be the solution. It is a less than perfect solution at best as I am expecting the form to return two large fields with significant formatted text that is then applied to the thread. I use the two separate editor fields so I can wrap a [HIDE] tag around on of them for enhanced membership content. Not having that is going to be sickening.

Maybe I need to look back at vB 4.2.5 patch level 4000 as a workable solution. Then I wouldn't have the spurious browser warnings and the Easy Forms 4.2.5 would work.


All times are GMT. The time now is 06:40 AM.

Powered by vBulletin® Version 3.8.12 by vBS
Copyright ©2000 - 2025, vBulletin Solutions Inc.

X vBulletin 3.8.12 by vBS Debug Information
  • Page Generation 0.06520 seconds
  • Memory Usage 1,775KB
  • Queries Executed 10 (?)
More Information
Template Usage:
  • (1)ad_footer_end
  • (1)ad_footer_start
  • (1)ad_header_end
  • (1)ad_header_logo
  • (1)ad_navbar_below
  • (2)bbcode_php_printable
  • (5)bbcode_quote_printable
  • (1)footer
  • (1)gobutton
  • (1)header
  • (1)headinclude
  • (6)option
  • (1)pagenav
  • (1)pagenav_curpage
  • (4)pagenav_pagelink
  • (5)pagenav_pagelinkrel
  • (1)post_thanks_navbar_search
  • (1)printthread
  • (10)printthreadbit
  • (1)spacer_close
  • (1)spacer_open 

Phrase Groups Available:
  • global
  • postbit
  • showthread
Included Files:
  • ./printthread.php
  • ./global.php
  • ./includes/init.php
  • ./includes/class_core.php
  • ./includes/config.php
  • ./includes/functions.php
  • ./includes/class_hook.php
  • ./includes/modsystem_functions.php
  • ./includes/class_bbcode_alt.php
  • ./includes/class_bbcode.php
  • ./includes/functions_bigthree.php 

Hooks Called:
  • init_startup
  • init_startup_session_setup_start
  • init_startup_session_setup_complete
  • cache_permissions
  • fetch_threadinfo_query
  • fetch_threadinfo
  • fetch_foruminfo
  • style_fetch
  • cache_templates
  • global_start
  • parse_templates
  • global_setup_complete
  • printthread_start
  • pagenav_page
  • pagenav_complete
  • bbcode_fetch_tags
  • bbcode_create
  • bbcode_parse_start
  • bbcode_parse_complete_precache
  • bbcode_parse_complete
  • printthread_post
  • printthread_complete