<![CDATA[WA Forums - All Forums]]> https://webassist-pro.com/WAforum/ Mon, 13 Apr 2026 06:15:40 +0000 MyBB <![CDATA[Reply to Bill Hobbs re PHP 8.2 Upgrade]]> https://webassist-pro.com/WAforum/showthread.php?tid=38 Mon, 22 Sep 2025 09:34:08 +0000 Mags]]> https://webassist-pro.com/WAforum/showthread.php?tid=38
The error:

Fatal error: Uncaught Error: Call to undefined function mysqli_init()

means that PHP can't find the mysqli_init() function, which only exists if the MySQLi extension is installed and enabled in your PHP environment.

Check if the MySQLi extension is installed - download the attached phpinfo.php file and upload it to your server. Access the page in the browser, then search the page for "mysqli".

If you don’t see it, the extension is not installed or not enabled.

You may need to ask your server supplier to enable it, or let me know if you need help. Once activated, check the phpinfo page again.

You should remove the phpinfo.php file once you've finished with it for security purposes.


.php   phpinfo.php (Size: 22 bytes / Downloads: 0) ]]>
The error:

Fatal error: Uncaught Error: Call to undefined function mysqli_init()

means that PHP can't find the mysqli_init() function, which only exists if the MySQLi extension is installed and enabled in your PHP environment.

Check if the MySQLi extension is installed - download the attached phpinfo.php file and upload it to your server. Access the page in the browser, then search the page for "mysqli".

If you don’t see it, the extension is not installed or not enabled.

You may need to ask your server supplier to enable it, or let me know if you need help. Once activated, check the phpinfo page again.

You should remove the phpinfo.php file once you've finished with it for security purposes.


.php   phpinfo.php (Size: 22 bytes / Downloads: 0) ]]> <![CDATA[not seeing database error]]> https://webassist-pro.com/WAforum/showthread.php?tid=37 Tue, 26 Aug 2025 17:18:26 +0000 bizpat (Patrice)]]> https://webassist-pro.com/WAforum/showthread.php?tid=37
My server was set to 8.1. Chat says WA was written for 7.4. I reset this domain to 7.4, made the connection file, then changed domain back to 8.1]]>
My server was set to 8.1. Chat says WA was written for 7.4. I reset this domain to 7.4, made the connection file, then changed domain back to 8.1]]> <![CDATA[Latest version of Chrome throwing errors for PVii js files]]> https://webassist-pro.com/WAforum/showthread.php?tid=31 Fri, 07 Feb 2025 15:33:21 +0000 David Buchholz]]> https://webassist-pro.com/WAforum/showthread.php?tid=31 https://developer.chrome.com/docs/web-pl...ing-unload, this is causing issues with a lot of PVII's scripts. In my case on the site I am working on both AMM and MBX are affected.

The fix is to change the unload event to before unload like so:

Code:
function P7_MBXaddLoad(){
var ie = P7_MBXgetIEver();
if (!document.getElementById || (ie > 0 && ie < 6)) {
return;
}
if (window.addEventListener) {
document.addEventListener("DOMContentLoaded", P7_MBXinit, false);
window.addEventListener("load", P7_MBXinit, false);
//window.addEventListener("unload", P7_MBXbb, false);
window.addEventListener("beforeunload", P7_MBXbb, false); // Changed from unload to beforeunload
document.addEventListener("keydown", P7_MBXkey, false);
window.addEventListener("resize", P7_MBXrsz, false);
} else if (window.attachEvent) {
document.write("<script id=p7ie_mbx defer src=\"//:\"><\/script>");
document.getElementById("p7ie_mbx").onreadystatechange = function(){
if (this.readyState == "complete") {
if (p7MBX.ctl.length > 0) {
P7_MBXinit();
}
}
};
window.attachEvent("onload", P7_MBXinit);
window.attachEvent("onunload", P7_MBXbb);
document.attachEvent("onkeydown", P7_MBXkey);
window.attachEvent("onresize", P7_MBXrsz);
}
}


Hope that helps]]> https://developer.chrome.com/docs/web-pl...ing-unload, this is causing issues with a lot of PVII's scripts. In my case on the site I am working on both AMM and MBX are affected.

The fix is to change the unload event to before unload like so:

Code:
function P7_MBXaddLoad(){
var ie = P7_MBXgetIEver();
if (!document.getElementById || (ie > 0 && ie < 6)) {
return;
}
if (window.addEventListener) {
document.addEventListener("DOMContentLoaded", P7_MBXinit, false);
window.addEventListener("load", P7_MBXinit, false);
//window.addEventListener("unload", P7_MBXbb, false);
window.addEventListener("beforeunload", P7_MBXbb, false); // Changed from unload to beforeunload
document.addEventListener("keydown", P7_MBXkey, false);
window.addEventListener("resize", P7_MBXrsz, false);
} else if (window.attachEvent) {
document.write("<script id=p7ie_mbx defer src=\"//:\"><\/script>");
document.getElementById("p7ie_mbx").onreadystatechange = function(){
if (this.readyState == "complete") {
if (p7MBX.ctl.length > 0) {
P7_MBXinit();
}
}
};
window.attachEvent("onload", P7_MBXinit);
window.attachEvent("onunload", P7_MBXbb);
document.attachEvent("onkeydown", P7_MBXkey);
window.attachEvent("onresize", P7_MBXrsz);
}
}


Hope that helps]]> <![CDATA[A new server threat: AI bots]]> https://webassist-pro.com/WAforum/showthread.php?tid=30 Wed, 22 Jan 2025 21:38:50 +0000 bizpat (Patrice)]]> https://webassist-pro.com/WAforum/showthread.php?tid=30
Solution was to create a robots.txt file with this inside:

User-agent: GPTBot
Disallow: /

User-agent: Amazonbot
Disallow: / 


HTH someone else.]]>
Solution was to create a robots.txt file with this inside:

User-agent: GPTBot
Disallow: /

User-agent: Amazonbot
Disallow: / 


HTH someone else.]]> <![CDATA[Extension Manager]]> https://webassist-pro.com/WAforum/showthread.php?tid=29 Sun, 19 Jan 2025 00:57:33 +0000 bizpat (Patrice)]]> https://webassist-pro.com/WAforum/showthread.php?tid=29
I encountered this a few weeks ago with a non-WA extension (P7). I received this information.

Gerry wrote:

The latest Adobe Creative Cloud update has introduced a file corruption issue in the Dreamweaver menus.xml and insertbar.xml files. This will cause extensions to not show in the Dreamweaver Insert menu and the Insert Panel. Hopefully Adobe will fix this soon.

You have a corruption in the underlying Dreamweaver files that now needs to be fixed.

1. Do NOT use the Anastasiy’s Extension Manager!

2. ONLY use the DMXzone Extension Manager.

3. Follow the instructions on the page link I sent. The Dreamweaver configuration folder is corrupt and needs to be replaced with a default configuration. The instructions here are very important, follow each step:

https://www.projectseven.com/products/ex...m#cc-issue  (this is no longer an active link)


First, be sure that you have re-started Dreamweaver after you renamed the configuration folder. Then shut Dreamweaver down.

In the DMXzone Extension Manager, if your extensions are listed as installed then you must first un-install each. Just click the X to the right of each extension. This will clear the extension database. Now you can install each one, one at a time.

Be sure that Dreamweaver is shut down during this operation.

~~HTH~~~

more notes

The missing link says to first shut down DW. Rename the config folder. Restart DW. Shut down DW. UNINSTALL all ext., then reinstall all extensions. Then restart DW.]]>
I encountered this a few weeks ago with a non-WA extension (P7). I received this information.

Gerry wrote:

The latest Adobe Creative Cloud update has introduced a file corruption issue in the Dreamweaver menus.xml and insertbar.xml files. This will cause extensions to not show in the Dreamweaver Insert menu and the Insert Panel. Hopefully Adobe will fix this soon.

You have a corruption in the underlying Dreamweaver files that now needs to be fixed.

1. Do NOT use the Anastasiy’s Extension Manager!

2. ONLY use the DMXzone Extension Manager.

3. Follow the instructions on the page link I sent. The Dreamweaver configuration folder is corrupt and needs to be replaced with a default configuration. The instructions here are very important, follow each step:

https://www.projectseven.com/products/ex...m#cc-issue  (this is no longer an active link)


First, be sure that you have re-started Dreamweaver after you renamed the configuration folder. Then shut Dreamweaver down.

In the DMXzone Extension Manager, if your extensions are listed as installed then you must first un-install each. Just click the X to the right of each extension. This will clear the extension database. Now you can install each one, one at a time.

Be sure that Dreamweaver is shut down during this operation.

~~HTH~~~

more notes

The missing link says to first shut down DW. Rename the config folder. Restart DW. Shut down DW. UNINSTALL all ext., then reinstall all extensions. Then restart DW.]]> <![CDATA[P7 IGM Image Gallery Magic]]> https://webassist-pro.com/WAforum/showthread.php?tid=27 Fri, 10 Jan 2025 17:54:24 +0000 LanaB]]> https://webassist-pro.com/WAforum/showthread.php?tid=27 LINK: http://www.dreambuildersofthefloridakeys...dream.html
I appreciate direction!
Thanks,
Lana]]> LINK: http://www.dreambuildersofthefloridakeys...dream.html
I appreciate direction!
Thanks,
Lana]]> <![CDATA[To link to Omni Panel and open it]]> https://webassist-pro.com/WAforum/showthread.php?tid=26 Sat, 04 Jan 2025 18:57:31 +0000 bizpat (Patrice)]]> https://webassist-pro.com/WAforum/showthread.php?tid=26 
https://www.shorehavenbhi.com/mental-hea..._3#p7OPM_1

so, after the page name, add
?opm
the panel name (third panel)
1_3#
and the name of the OPM

another example:
https://www.shorehavenbhi.com/mental-hea..._5#p7OPM_1

opens the 5th panel  



(if there were 2 OPMs on the page the second one would be called 
OPM_2)]]> 
https://www.shorehavenbhi.com/mental-hea..._3#p7OPM_1

so, after the page name, add
?opm
the panel name (third panel)
1_3#
and the name of the OPM

another example:
https://www.shorehavenbhi.com/mental-hea..._5#p7OPM_1

opens the 5th panel  



(if there were 2 OPMs on the page the second one would be called 
OPM_2)]]> <![CDATA[FX Zoom Fix]]> https://webassist-pro.com/WAforum/showthread.php?tid=25 Sat, 04 Jan 2025 18:51:32 +0000 bizpat (Patrice)]]> https://webassist-pro.com/WAforum/showthread.php?tid=25

/*
****************************
PVII Image Effects Magic
by Project Seven Development
www.projectseven.com
CSS Styles
*****************************
*/

img.p7IFX {
position: relative;
}
img.ifx-on {
z-index: 999;
}]]>

/*
****************************
PVII Image Effects Magic
by Project Seven Development
www.projectseven.com
CSS Styles
*****************************
*/

img.p7IFX {
position: relative;
}
img.ifx-on {
z-index: 999;
}]]> <![CDATA[Close panels on OMNI]]> https://webassist-pro.com/WAforum/showthread.php?tid=24 Sat, 04 Jan 2025 18:48:51 +0000 bizpat (Patrice)]]> https://webassist-pro.com/WAforum/showthread.php?tid=24
Add to core.css

<!--custom -->
.opm-panel {position:absolute;left:-9000px;top:-9000px;overflow:hidden;visibility:hidden;width:100%;}
.opm-panel-wrapper {position:relative;overflow:hidden;}
.opm-panel-layout {position: relative;width: 100%;height: auto;}


and then on the page, depending on which panel will be the close, this is inline
this must be specific to the panels

example (to have panel 7 closed)



<style type="text/css">
#p7OPMpn_1_7,
#p7OPMpn_1_7 *
{
padding: 0;
}
#p7OPMpn_1_7 .opm-panel-content {
height: 0px;
}
</style>]]>
Add to core.css

<!--custom -->
.opm-panel {position:absolute;left:-9000px;top:-9000px;overflow:hidden;visibility:hidden;width:100%;}
.opm-panel-wrapper {position:relative;overflow:hidden;}
.opm-panel-layout {position: relative;width: 100%;height: auto;}


and then on the page, depending on which panel will be the close, this is inline
this must be specific to the panels

example (to have panel 7 closed)



<style type="text/css">
#p7OPMpn_1_7,
#p7OPMpn_1_7 *
{
padding: 0;
}
#p7OPMpn_1_7 .opm-panel-content {
height: 0px;
}
</style>]]> <![CDATA[Centering P7 Menus]]> https://webassist-pro.com/WAforum/showthread.php?tid=23 Sat, 04 Jan 2025 18:46:02 +0000 bizpat (Patrice)]]> https://webassist-pro.com/WAforum/showthread.php?tid=23
p7 centermenu
.p7AMM.amm-responsive li {
text-align: left !important;
display: block;
max-height: 700777px;
}

to this:



.p7AMM.amm-responsive li {
text-align: center !important;
display: block;
max-height: 700777px;
}]]>
p7 centermenu
.p7AMM.amm-responsive li {
text-align: left !important;
display: block;
max-height: 700777px;
}

to this:



.p7AMM.amm-responsive li {
text-align: center !important;
display: block;
max-height: 700777px;
}]]> <![CDATA[Set Height of Slide Out Panel (SOP)]]> https://webassist-pro.com/WAforum/showthread.php?tid=22 Thu, 02 Jan 2025 15:29:10 +0000 David Buchholz]]> https://webassist-pro.com/WAforum/showthread.php?tid=22 #p7SOP_1 {
height: 70%;
}
The height of the SOP will now be 70% of the browser window.
You can also add a top position to this rule if you want the (now shortend) SOP to be centered vertically. Just set the top position to 15% (one half of 30%) so the rule now looks like this:
#p7SOP_1 {
height: 70%;
top: 15%;
}

Note that you cannot, and should not, set the height greater than the height of the browser window. This will prevent full access to all of the overflowed content.]]> #p7SOP_1 {
height: 70%;
}
The height of the SOP will now be 70% of the browser window.
You can also add a top position to this rule if you want the (now shortend) SOP to be centered vertically. Just set the top position to 15% (one half of 30%) so the rule now looks like this:
#p7SOP_1 {
height: 70%;
top: 15%;
}

Note that you cannot, and should not, set the height greater than the height of the browser window. This will prevent full access to all of the overflowed content.]]> <![CDATA[Flex Grid Magic (FGM) Column Widths]]> https://webassist-pro.com/WAforum/showthread.php?tid=21 Thu, 02 Jan 2025 15:27:10 +0000 David Buchholz]]> https://webassist-pro.com/WAforum/showthread.php?tid=21 30% = 3 per column max
22% = 4 per column max
17% = 5 per column max]]> 30% = 3 per column max
22% = 4 per column max
17% = 5 per column max]]> <![CDATA[Change LBM Column Order On A Mobile Device]]> https://webassist-pro.com/WAforum/showthread.php?tid=20 Thu, 02 Jan 2025 15:25:18 +0000 David Buchholz]]> https://webassist-pro.com/WAforum/showthread.php?tid=20
Add this style rule to the end of your exception style sheet:

@media only screen and (min-width: 0px) and (max-width: 700px) {
.lbm-col-wrapper {
display: grid !important;
}
.lbm-column:nth-child(1) {order: 2;}
.lbm-column:nth-child(2) {order: 1;}
.lbm-column:nth-child(3) {order: 3;}
}

This switches the layout to CSS Grid spec and sets the different order.]]>
Add this style rule to the end of your exception style sheet:

@media only screen and (min-width: 0px) and (max-width: 700px) {
.lbm-col-wrapper {
display: grid !important;
}
.lbm-column:nth-child(1) {order: 2;}
.lbm-column:nth-child(2) {order: 1;}
.lbm-column:nth-child(3) {order: 3;}
}

This switches the layout to CSS Grid spec and sets the different order.]]> <![CDATA[P7 - links to help files]]> https://webassist-pro.com/WAforum/showthread.php?tid=19 Mon, 23 Dec 2024 20:37:00 +0000 bizpat (Patrice)]]> https://webassist-pro.com/WAforum/showthread.php?tid=19
Courtesy of denniscallan on Adobe Community forum

https://community.adobe.com/t5/dreamweav.../2#M229689

https://onedrive.live.com/?authkey=%21AL...2AC9BBAD5B]]>
Courtesy of denniscallan on Adobe Community forum

https://community.adobe.com/t5/dreamweav.../2#M229689

https://onedrive.live.com/?authkey=%21AL...2AC9BBAD5B]]> <![CDATA[Availability]]> https://webassist-pro.com/WAforum/showthread.php?tid=18 Thu, 05 Dec 2024 16:24:52 +0000 David Buchholz]]> https://webassist-pro.com/WAforum/showthread.php?tid=18
Thanks,

Dave Buchholz.
I-CRE8]]>
Thanks,

Dave Buchholz.
I-CRE8]]>