I have recently upgraded my EE magento 2.2.6 to 2.3.2. The category pages are are showing error on front-end:
Exception #0 (DomainException): Undefined factory mysql
Also some of my cms pages showing error (possibly due to newly added functionality of Pagebuilder (turning it off doesn't resolve the issue) by Magento):
Argument 2 passed to Magento\PageBuilder\Plugin\Filter\TemplatePlugin::afterFilter() must be of the type string, null given, called in /vendor/magento/framework/Interception/Interceptor.php on line 146
Anyone??
Resolved: For part 1: It was some configuration issue, so I downloaded the core_config_data table and replaced it with my staging site one
For part 2: I was using VladmirPopov webforms extension, it was causing the issue in cms pages, so downloaded the latest version of webforms extension and replaced it.
Related
primefaces showcase deployed on tomcat style not loaded
Downloaded the source code from below link branch 8.0
https://github.com/primefaces/primefaces-showcase
deployed in tomcat the site is misalligned the styles are not loaded see image attached.
what i am missing why the site is not aligned.
TOMCAT: NO errors in tomcat logs
Glassfish : Error occurred during deployment: Exception while loading the app : java.lang.IllegalStateException: ContainerBase.addChild: start: org.apache.catalina.LifecycleException: org.apache.webbeans.exception.WebBeansDeploymentException: java.lang.NullPointerException. Please see server.log for more deta
Wildfly : {"WFLYCTL0080: Failed services" => {"jboss.deployment.unit.\"primefaces-8.0-SNAPSHOT.war\".undertow-deployment.UndertowDeploymentInfoService" => "java.lang.ClassNotFoundException: org.primefaces.webapp.FileUploadChunksServlet from [Module \"deployment.primefaces-8.0-SNAPSHOT.war\" from Service Module Loader]
Caused by: java.lang.ClassNotFoundException: org.primefaces.webapp.FileUploadChunksServlet from [Module \"deployment.primefaces-8.0-SNAPSHOT.war\" from Service Module Loader]"}}
As long as it deploys in one of the server i am good to go.
So the first thing you did is check if org.primefaces.webapp.FileUploadChunksServlet is actually in the PrimeFaces 8 jar and noticed it is not there. Then you checked the PrimeFaces 8 tag in the source of PrimeFaces and noticed it is also not there. Then you checked the PrimeFaces Master (8.0.x) and noticed it IS there Then you checked the PrimeFaces showcase source to see if there, besides the 8.0.x branch there is a 8.0 tag and noticed tere is not. So your conclusion was that the 8.0.x showcase is up to date with the master and an explicit version of the showcase at the time of releasing PrimeFaces 8.0 is missing.
So you then decided you have three options
In the showcase source, go to the point in time of releasing PF 8 and download the source of that 'snapshot'
File an issue in the PrimeFaces showcase https://github.com/primefaces/primefaces-showcase/issues to request a tag to be made (maybe in retrospect even)
Do both
You then decided to do both and was happy because you could run the showcase locally and made the world a better place since you helped others in the future when the wanted to use the showcase source with a PrimeFaces community release.
I have recently upgraded a .net Core (2.1) / Angular 6 SPA app to the latest versions. I seemed to have done everything correctly at one point, but I made a change that broke the http (port 5000) app. I get an error:
vendor.js:1 Uncaught ReferenceError: module is not defined
at vendor.js:1
This is the first line of the vendor.js file. When I run the app using port 5001 (https), everything seems to work fine. I cannot figure out why there is a difference in the two websites as they are hitting the same code base.
To begin this upgrade, I started with the official dotnet core 2.1 Angular SPA and upgrade angular from 5 to 6.
I had this exact error and fixed it by changing the port number for the App URL in the Project Properties.
Hope this helps, however I'm still not sure what caused the issue.
I'm seeing dozens of entries, daily, in my cgi_error_log file like this:
20151214T183710: www.example/index.php
Failed loading /usr/local/lib/ioncube/ioncube_loader_lin_5.2.so: /usr/local/lib/ioncube/ioncube_loader_lin_5.2.so: wrong ELF class: ELFCLASS32
Failed loading /usr/local/Zend/lib/ZendExtensionManager.so: /usr/local/Zend/lib/ZendExtensionManager.so: wrong ELF class: ELFCLASS32
I changed the URL in the error message because the site is not yet ready for the public and I don't want any links to the site or even text in posts like this laying around.
As the site is still in testing, these messages are coming from my accessing pages and all of the pages have loaded correctly.
What does this message mean? I have no clue other than that ioncube is some sort of PHP Encoder.
Could this have something to do with the 32bit version of ioncube being run on a 64bit system? I've found references to that sort of problem.
Did some more digging - could this be happening because the version of PHP on the server is not 5.2? Error about ioncube shows 4.2 in the file name.
The version I'm using on the server if 5.5. They have 5.3 and 5.6.
If they had 5.2 I'd give it a try but it is not available.
More digging - found this set in my php.ini file for all my sites.
[Zend]
zend_extension = /usr/local/lib/ioncube/ioncube_loader_lin_5.2.so
zend_extension_manager.optimizer=/usr/local/Zend/lib/Optimizer-3.2.0
zend_extension_manager.optimizer_ts=/usr/local/Zend/lib/Optimizer_TS-3.2.0
zend_optimizer.version=3.2.0
zend_extension=/usr/local/Zend/lib/ZendExtensionManager.so
zend_extension_ts=/usr/local/Zend/lib/ZendExtensionManager_TS.so
So - do I need to install newer versions of one or more of the items listed above?
If so - where do I start and can I do it myself or does the hosting company staff have to do it?
I am a newbie and I am facing some strange issues with my Joomla 3.1.1 installation. Whenever I try to do a Joomla global check-in, I get the following error:
SQL=SELECT module FROM SOM_modules WHERE id = table-name
*This is true for all tables
Further, when I try to edit the template custom CSS file from the back-end, I get the following error:
SQL=SELECT module FROM SOM_modules WHERE id =
MTAwNTE6Y3NzL3J0X2RpYW1ldHJpY19yZXNwb25zaXZlLWN1c3RvbS5jc3M=
I am facing the same error even when I try to purge Joomla cache.
In all cases, it only says "An error has occurred" and there is a preceding 0 before the errors above. I presume that is the SQL error 0.
Kindly help. I have checked the forum and googled for hours but can't find any solution. I have also tried resetting directory and file permissions even to 777 - to test, still no luck.
Config Details:
Joomla! version: 3.1.1
PHP version: 5.3.1
MySQL version: 5.5.31
Host: Private VPS
Finally, this issue is resolved. The issue was with another extension called "Content Statistics". Somehow this extension messed up the entire backend. It took quite a lot of time to figure out which extension had caused the problem
After uninstalling the extension and all related modules and plugins, the site has become fully functional again. No more SQL=0 errors and I am being able to edit all css files from the backend. – Mangesh
I have a web server with MONO 2.10.2 (fast-cgi) on a CentOS 6 box. Running a plain-vanilla MVC 3 site works great. However, when I add MySql.Data, it gives me a not-so-helpful error:
System.IO.FileLoadException: The assembly name is invalid.
My DLLs are in the right place. They're referenced properly. Everything has been done correctly, but Mono still complains that it can't find an assembly without telling me which one. The problem occurs after simply adding a reference to MySql.Data and without changing any code. I've looked through the MySql.Data source solution and the references that it needs seem to exist on the web server.
I understand other people have the same problem. I am happy to debug it myself, but I'm new to Mono and I can't figure out how to get a more-detailed error messages. I've checked Mono's site for instructions to enable more detailed logging, but their docs assume a certain base knowledge about Mono that I do not have.
Is there a way to get more detailed information when Mono fails to load an assembly?
I'm not sure if these details matter, but just in case...
- Mono: 2.10.2 (served via fastcgi-mono-server4)
- MySql: Connector.Net 6.4.4.0 (from the v4 set in the .Net & Mono download)
- Webserver: NGINX 1.0.11
- OS: CentOS 6
If you can get a "test case" that compiles to an application, try:
MONO_LOG_LEVEL="debug" MONO_LOG_MASK="dll" mono my_app.exe
Or just temporarily edit your CGI script so that it sets those two variables. Check the logs - you should see what is not loaded propely.