This is a very peculiar problem. A client's Magento 2.2.6 EE has emptied its cms page table twice today (sometime between 5pm EST and 5:20pm and again between 11:00pm and 11:30pm). I have disabled magento's crontab until a solution presents itself. The action log also has no records of access.
I combed through the action logs but nothing there stood out.
Has anyone come across this before? And how would I debug this? The system is setup to make hourly db snapshots so it's just a headache at this point.
Way interesting. I would start logging your db calls to find when and how the tables are emptied.
Check out this StackOverflow answer using MySQL.
If you get the exact query and user info, if Magento system user, search your whole install for that query reference.
Another option, if you have Magento plugins, disable all and see if the issue presents itself again.
Does the index reset when the table is emptied? If so, try disable truncate permissions from the Magento user and see what error is thrown when this action is attempted again. This would be a way to find the source of the call using the Magento error log.
Related
I am working on apereo CAS 5.3.x, and in my application Login operation expects 3 data elements - username, password and a group code.
I need to add group code combo box. this combo box will get data from the database and at the time of submission need to submit the selected data from combo box also.
I have tried the code from this URL https://apereo.github.io/2019/02/25/cas61-custom-login-fields/ also.
but it is not working.
can anyone help me on this issue?
I have tried the code from this URL https://apereo.github.io/2019/02/25/cas61-custom-login-fields/ also. but it is not working.
The reason it may not be working is that the document quite early on states the following:
Our starting position is based on:
CAS 6.1.x
That doesn't seem like it would match your CAS version, which as you state is 5.3.x.
So for that article to work, you need to be on the appropriate CAS version, and then try it out.
PS When you do, avoid phrases such as "it's not working". "It doesn't work" doesn't work. Please clearly state the problem, the issue, attach logs, describe versions, changes made, etc. This post might share a few points on how to troubleshoot and share results.
I am using PrestaShop 1.7.5.2 and recently changed my server & now the problem is that in my admin few pages are not working like "Products, Invoices, Stocks, Module Manager, Module Catalogue, Theme Catalogue etc.
My front end is working fine.
I have read almost all the content available but was not able to find exact solution to it.
Any help will be highly appreciated
Thanks,
GC
Edited just now by gauravchawla18 (see edit history)
Your database is incomplete. At least ps_translation table is missing.
Please check your database import.
I've been using Gravity Forms with no problems for a while, but today I'm receiving this error reading the following:
There was an issue creating your form.
Here is a screenshot of what the error looks like.
When I click on the System Status button to get more information, I see that the Database section has a red x reading the following:
The database is currently being upgraded to version 2.4.14.4. Current Status: Error Migrating Entry Headers: Table 'local.wp_rg_lead' doesn't exist NAN% complete. Force the upgrade
Here is a screenshot of the error above:
I click on the Force the upgrade button, but it has no affect on the issue.
Would anyone have any experience in solving this issue with Gravity Forms for WordPress? Thanks a lot!
I faced simillar issue on one of my sites but after sometime i manage to
solve the issue by following steps.
Export gravity forms tables from database.
Export forms and entries from from wp admin
Drop tables of gravity forms from database.
Re activate/ install gravity forms in wp admin.
Import gravity forms and entries in wp admin.
Thats it problem is solved and now you can create new gravity forms without any issue.
Uninstall Gravity Forms via the plugin General Settings page (Settings > Uninstall)
Reactivate the plugin again via plugins page.
As of the time of this posting, GF does not drop tables on plugin reactivation or deletion via the plugins page.
Similarly it will not create the necessary tables on reactivation and even reinstallation after manual removal of problematic tables from the DB.
GF will only drop tables after uninstalling via the plugin settings, at which point GF will create the required tables again upon next activation or installation.
It's been this way for a long time now: https://legacy.forums.gravityhelp.com/topic/error-saving-form#post-70107
I have actual the latest TYPO3 6.2 version ... 6.2.31 ... I know ... working on upgrade.
But now I have a google hack which replaces Links in Google with Viagra stuff. Had this several weeks ago thought I fixed it with update from 6.2.9 to 6.2.31
There is unkown code in Core .. Does any Body knows this and can help me fix the hole?
last time it was here:
/data/www/domain/public/typo3/typo3/sysext/cms/tslib/index_ts.php
Thanks at all
Please follow the TYPO3 Security Guide which means that if your website is hacked you must take it offline, check the site, find the security issue and then bring it only.
If your website is hacked, not only your server and data is at risk but every user who visits your website. Especially if users trust you and your knowledge, you should take that issue serious.
Most of the time I have seen this issue one of the following problems occurred:
Hacked FTP account
Security issues in custom or 3rd party extensions.
I'd like to update (e.g. dates or upcoming events etc.) in some tables in my database automatically before loading the rest of the page. For example the first time every Monday someone gets on the website.
Before I used joomla I had a php-script which I included at the beginning of every page and that worked pretty well.
But with joomla I don't know where to insert the (adjusted) script. Should I create a (content) plugin? But where/how would I trigger it?
Thank you
I got it working by using a cron job that calls a view especially made for this task. Using the URL with &format=raw so that no unnecessary joomla html gets loaded