Fatal error: Call to undefined function imap_open() in /home/tattoo/domains/thetattooforum.com/public_html/dbtech/vbmail/includes/class_imap.php on line 87
i setup a bounce email address and confirmed that emaisl are coming into that mailbox in outlook by setting it up and it is working correctly.
i added the same details into the bounce email collector and i get nothing.
if i manually run the scheduled task it just shows the title "DragonByte...
reply from vbet for further info this is how the system was working
Integration vBSEO with vBET works by replacing vBSEO functions on vBET functions. See: do-not-upload/readme.html->Integration with other mods->vBSEO Integration. Functions vBET translate text and parse it properly (using vBSEO...
when a new notification abotu a mention etc appears under notifications it links to View Profile: bradcymru - Tattoo Forums - Discussion for the Tattood and Pierced
the actual url which shows when i hover on the tab is View Profile: turbosatan - Tattoo Forums - Discussion for the Tattood and...
ok so they ahve said they do not have plans to support dbseo currently so i will need to figure this out myself.
Are you able to provide suggestions on what changes to make for DBSEO to send various rules through to VBET as and when translations are happening?
The plugin was working with VBSEO...
the current reply from vbet is
We currently do not support dbseo.
Change in seo on dbseo is not so simple. In addition to adding the rules you must using vBET translate phrases from seo and replace them. For this purpose should be to create the appropriate controller or hooks.
Can i put you in...
it means replication may not work. the advised method to use is mixed not statement.
also as i am getting approx 3-4 entries per second from this its a bit difficult to ignore it.
can you not modify the statement to mixed so it doesnt cause the errors...
hopefully my thread doesnt get deleted this time
i am getting thousands of these entries into the syslog on a mariadb nginx server.
could you advise where to modify this code to stop the error.
Apr 13 06:38:53 srv1 mysqld: 150413 6:38:53 [Warning] Unsafe statement written to the binary log...
dbseo seems to be using more and more resources all the time.
this only really started a month or so ago. i updated vbulletin and dbseo to latest versions but still ahve lots of dbseo processes on the server all the time.
Are there any optimisations i can make to stop it from being so resource...