itpixie

Hello @yogajegstudio and The Gutenverse Team,

Thank you very much for getting back to me, and for clarifying the new changes in 3.0.0.

To answer your questions…

Share screenshots of the issues where the form is not working, is there any error shown.

Unfortunately, in my attempt to clean up the patterns that was getting the “Form Action Required” error and the orphaned forms, I deleted those patterns. Here’s a screenshot of where that error would have been, and I will describe what led to the issue…

1. I started my site with the Kavana theme and made necessary styling and function modifications to suit my needs.
2. Since I cannot actually edit the stock patterns that came with the theme — they are all locked, I made duplicates of the stock patterns that I need and made changes to the duplicates created by me.
3. Prior to 3.0.0 update, I created one form action for email address collection (Form ID 822, “PB Newsletter Signup”), and used it in three different patterns (“PB Home Popup”, “PB Email Signup” and “PB Single Post Content”). All of these patterns are duplicates of selected Kavana stock patterns, linked to Form ID 822 and with my stylistic customization.
4. When the plugin was updated to 3.0.0, I was notified about the duplicate form actions were created, and modifications to these clones wouldn’t change the original. I noticed each clone had ambiguous titles like “PB Newsletter Signup Clone 1”, I changed the titles of these clones to more accurately reflect which clone is linked to which pattern (see example below).
   • PB Home Popup – PB Newsletter Signup (ID 822, original form, no title change)
   • PB Email Signup – PB Newsletter Signup Main (ID 20xx, clone 1, title changed)
   • PB Single Post Content – PB Newsletter Signup Post (ID 20xx, clone 2, title changed)
5. However after I closed the updated pattern and later reopened it for more edits, I saw the error “This form action does not exist on this site” error, and there was the Create Form Action button.
6. So I clicked the “Create Form Action”, the form action edit popup opened, and had to fill in all the fields.
7. Whenever I opened PB Email Signup or PB Single Post Content patterns, the Connected Form Action would flash then the “This form action doesn’t exist on this site” error popped up almost immediately and covered the Connected Form Action section. I repeated Step 6 a few times, and ended up created multiple clones of PB Newsletter Signup Main and PB Newsletter Signup Post forms. Each of these cloned forms have unique Form ID.
8. I eventually created brand new forms for the patterns-in-questions (Form IDs 2076 & 2108)

https://photos.app.goo.gl/2p7kRBChkJHYFm4W9

Did the cloned/copied form actions end up with missing or incomplete data?

So the forms were actually working as far as I can tell — When someone submit an email address via the form, the data is captured and saved in the form database. What’s not working was on the admin end, whenever I opened the pattern for edits, I would see those error message. The “Connected Form Action” section would flash for half a second, that the “This form action does not exist on this site” would pop up over it, and I would be asked to Create Form Action. So I was no longer able to edit the form action.

Is this issue occurring only with the stock theme patterns (like the newsletter sign-up), or does it happen when you create entirely new forms from scratch?

This issue happened to patterns that were duplicates of the stock theme patterns. As I mentioned before, I created a new form (Form ID 822) initially, and linked this form to multiple patterns (duplicates of stock patterns). After the plugin was updated, clones of Form ID 822 was created, and it was these clones that I was experience the error.

The entirely new forms that I created (Forms IDs 2076 and 2108) do not have any issues. I am able to edit them without any errors. I am also able to delete any new form actions that I create now, in the Connected Form Action section.

Any other clues that might help us

The “This form action does not exist on this site” error seems to be isolated to the clones of Form ID 822. Based on my own observations, it seems the cloned forms, created when the plugin was updated, somehow get disconnected to the patterns they supposed to connect to.

The original form, Form ID 822, does have any issue or error.

My main issue at this point is trying to find a way to delete all the orphaned forms. Since they don’t seem to linked to any pattern, I cannot delete them through Edit Pattern –> Connected Form Action. And there is no way to view all the “Tracked Forms” in an easily accessible way. The only way I can see a complete list of them is through a drop-down menu on the “Entries from All Forms” page.

Personally I would like to have the ability to easily see a list of “Tracked Forms” outside of the Entries page. I would also like the ability to mange the form outside of Edit Pattern –> Connected Form Action. I understand the need to enforce and protect the connection between forms and patterns. But in a case like mine, when those connections were corrupted, and no way to clean up the corrupted data, it is a bit frustrating.

I hope I have provided the information you need to investigate the issue, and I hope everything I said made sense. I’m sorry I don’t have the screenshots you asked for, but please feel free to reach out if you need additional information.

Thank you very much for looking into this.

Sincerely,

Amy (itpixie)

Hello Helix,

Thank you so much for the Firebug info. One of the sites that I’m having problem initializing the database has the following SQL error:

<h1>CDbException</h1>
<p>CDbCommand failed to execute the SQL statement: SQLSTATE[HY000]: General error: 1005 Can’t create table ‘fireflys_wordpressdb.ffsd_osefirewall_acl’ (errno: 121). The SQL statement executed was:

CREATE TABLE IF NOT EXISTS ffsd_osefirewall_acl (
id INT(11) NOT NULL AUTO_INCREMENT ,
name VARCHAR(300) NOT NULL ,
status TINYINT(1) NOT NULL ,
datetime DATETIME NOT NULL ,
score TINYINT(3) NOT NULL ,
country_code CHAR(2) NULL DEFAULT NULL ,
host VARCHAR(300) NULL DEFAULT NULL ,
notified TINYINT(1) NULL DEFAULT NULL ,
referers_id INT(11) NOT NULL ,
pages_id INT(11) NOT NULL ,
visits INT(11) NOT NULL ,
PRIMARY KEY (id) ,
INDEX idx1_oseacl (referers_id ASC) ,
INDEX idx2_oseacl (pages_id ASC) ,
CONSTRAINT fk1_oseacl
FOREIGN KEY (referers_id )
REFERENCES ffsd_osefirewall_referers (id )
ON UPDATE CASCADE,
CONSTRAINT fk2_oseacl
FOREIGN KEY (pages_id )
REFERENCES ffsd_osefirewall_pages (id )
ON UPDATE CASCADE)
ENGINE = InnoDB
AUTO_INCREMENT = 1
DEFAULT CHARACTER SET = utf8 (/home/fireflys/public_html/dealers/wp-content/plugins/ose-firewall/framework/db/CDbCommand.php:541)</p>

#0 /home/fireflys/public_html/dealers/wp-content/plugins/ose-firewall/framework/db/CDbCommand.php(376): CDbCommand->queryInternal('', 0, Array)
#1 /home/fireflys/public_html/dealers/wp-content/plugins/ose-firewall/framework/oseframework/db/oseDB2.php(58): CDbCommand->query()
#2 /home/fireflys/public_html/dealers/wp-content/plugins/ose-firewall/framework/oseframework/installer/wordpress.php(43): oseDB2->query()
#3 /home/fireflys/public_html/dealers/wp-content/plugins/ose-firewall/protected/models/DashboardModel.php(159): oseInstaller->createTables('/home/fireflys/...')
#4 /home/fireflys/public_html/dealers/wp-content/plugins/ose-firewall/protected/models/DashboardModel.php(56): DashboardModel->createTables()
#5 /home/fireflys/public_html/dealers/wp-content/plugins/ose-firewall/protected/controllers/DashboardController.php(34): DashboardModel->actionCreateTables()
#6 /home/fireflys/public_html/dealers/wp-content/plugins/ose-firewall/framework/web/actions/CInlineAction.php(49): DashboardController->actionCreateTables()
#7 /home/fireflys/public_html/dealers/wp-content/plugins/ose-firewall/framework/web/CController.php(308): CInlineAction->runWithParams(Array)
#8 /home/fireflys/public_html/dealers/wp-content/plugins/ose-firewall/framework/web/CController.php(286): CController->runAction(Object(CInlineAction))
#9 /home/fireflys/public_html/dealers/wp-content/plugins/ose-firewall/framework/web/CController.php(265): CController->runActionWithFilters(Object(CInlineAction), Array)
#10 /home/fireflys/public_html/dealers/wp-content/plugins/ose-firewall/framework/web/CWebApplication.php(282): CController->run('createTables')
#11 /home/fireflys/public_html/dealers/wp-content/plugins/ose-firewall/framework/oseframework/ajax/oseAjax.php(28): CWebApplication->runController('dashboard/creat...')
#12 [internal function]: oseAjax::runAction('')
#13 /home/fireflys/public_html/dealers/wp-includes/plugin.php(406): call_user_func_array('oseAjax::runAct...', Array)
#14 /home/fireflys/public_html/dealers/wp-admin/admin-ajax.php(72): do_action('wp_ajax_createT...')
#15 {main}

There are 2 WordPress installs using the same database, though each has their own set of tables (with different table prefix). Would that be the reason (2 WP installs using the same database) I’m encountering the sQL error? I had no problem initializing OSE Firewall database/tables on the 1st WP install.

My other question is:
Is there a way to force database initialization again, other than deleting the existing OSE Firewall tables?

Thanks,
itpixie