Laravel Backpack "Cannot find 'relationship' field view in any of the regular locations" - laravel-backpack

I bought backpack pro, in my local development environment it works, but online I get this error:
"Cannot find 'relationship' field view in any of the regular locations"
I published all vendor via FTP.
Any idea? Thanks

Sounds like you’re using the “realtionship” field type but do not have the PRO addon installed, that actually provides that field.
You can see a breakdown of the free vs paid features here: https://backpackforlaravel.com/docs/5.x/features-free-vs-paid
To fix this, you can either:
A) purchase and install Backpack PRO;
B) replace the “relationship” field with a FREE alternative like “select” or “select_multiple” if they support your type of Eloquent relationship;

I think he bougth the PRO, as stated in his first sentence.
Make sure you have your licence key set in your Production Environment .env file.
Can you check your vendor/backpack folder and see what packages are inside? If pro is there, can you see the contents ?
Since you told you used ftp to upload your files is possible that you don't have access to composer ? If you do, what's the output of composer why backpack/pro ?
Cheers

Related

Invalid login, please try again after upgrade from 3.5.10 to 3.6.8

I have created an identical copy of our production instance to my local environment running XAMPP and I am trying to do the following:
After upgrading Moodle from 3.5.10 to 3.6.8 and restoring all plugins etc. I am unable to login. Before upgrading to 3.6.8, I had already performed the following upgrades,
3.4.1 -> 3.4.9
3.4.9 -> 3.5.10
and everything worked fine during those 2 upgrades. I followed exactly the recommended upgrading method as described in moodle's docs.
After successfully upgrading to 3.6.8, I successfully passed the step about the server requirements for the correct php mysql and db versions, I then successfully passed the next step as well for upgrading the database and made sure that all the plugins are fine and had no errors (just some warnings about a few plugins that can be updated to newer version) and after that step finished too, I then got back to the /admin/index.php screen asking me to login. That seemed weird to me because during the previous updates, it never asked me to login after completing the upgrading, but I said, ok. i'll just login. So after trying to login i am constantly getting the message "Invalid login, please try again"
I have tried almost anything here and by anything I mean the following.
First of all, I checked my hashed password in the local database and it is exactly the same with my hashed password in production database.
I then read an article that from moodle 3.1 the logintoken was introduced and since we use the mb2nl theme, I supposed that I just have to add the new input hidden field for this logintoken to the login form but the field was already there and again that was not the issue.
I am at a point where I cannot think of what else might be wrong and I am stuck.
A few more information about our whole setup, we have a Joomla website and our moodle users are actually coming from Joomla, Therefore we use a plugin named Joomdle which connects these 2 CMSs. Our users register to our Joomla website and the Joomdle plugin sends the credentials to moodle and the user is being created to the moodle CMS as well and an entry is being created in the moodle's "user" table. The difference is that moodle generates a different hashed password from the hashed password that joomla does. Anyway, there were no problems at all with logins or anything else since I tried logging in with multiple user accounts in moodle and all worked fine, before upgrading to version 3.6.8.
This is not a Joomdle issue since I already checked this by completely removing Joomdle and this is not the cause. This is probably coming from moodle core but since moodle has NO error reporting or logging at all, I really cannot understand what this is.
To exclude one more matter linked in this question, I already checked and made sure that moodle's password salt is the same both in production and local environments.
I am not sure what is going on here and this is why I desperately need some help from experts.
Solution:
I was able to solve this problem but forgot to come back here and give the solution.
The problem was that, as I said above, we are using the mb2nl theme and the theme's login form did not include the hidden input field to create the logintoken.
On my question above I write somewhere in the middle "I supposed that I just have to add the new input hidden field for this logintoken to the login form but the field was already there and again that was not the issue". I was looking at the wrong place. The login form that I was looking at, was the Moodle's itself login form and not the theme's login form.
I then found the login form in the theme's files and the logintoken hidden input field was indeed missing from there. I added it and then I was able to login normally.
Happened to me today. Executing the cron.php cli script trigered again the upgrade process and solved my problem.

Object ID conflict in extensions in AL (Business Central OnPremises)

I'm a beginner in Dynamics Nav/Dynamics365/Business Central developing extensions in AL and I'm having a problem that I don't know how to solve it 'easily'.
I am working with 2 projects in Visual Studio Code at the same time in one workspace (previously I tried it in multiple workspaces) and there are 2 'pageextension' objects with ID 50100.
I'm having the following error:
The application object of type 'PageExtension' with the ID '50100' is defined in multiple apps. The apps are: Reports by myName 2.1.0.0; Workspace2 by myName2 1.0.0.0.
I know this error could be fixed changing the object ID but I think it should exist another solution.
Does this mean that if someone publishes and install an extension and then try to publish and install mine, will BC OnPrem not allow them to work with the second?
thank you in advance
The range you describe should only be used for customisations.
When publishing for AppSource, you will get a specific number range for your app.
If you intend to use multiple apps for customisations, you should divide the range and make sure you do not use double id's.

How to create an ATG store?

I have been studying ATG for about 4 months and now I am facing a problem: even going through the documentation I can't find any document that can clearly explain how I can create a new empty store.
I know that I need to have my database users and schemas, the application server scripts (I'm using weblogic) and the module in Eclipse. But I can't find anywhere how to create a new store, implement it from the beginning and see the result in the browser.
There is no such document for ATG. You either need to start from the Commerce Reference Store and customise that (in versions prior to ATG 11 would would strongly suggest not to use the CRS as your basis for a new site) or you can look at what the CRS executes for the runAssembler command, remove the CRS specific modules from that and then create, and include your own modules for the Storefront and your source code.
There is no empty store you can install and run. You have to build one. Or you can install CRS, which is not empty, but it is relatively straightforward to install and can be customized.
The documentation to follow:
http://docs.oracle.com/cd/E52191_02/CRS.11-1/ATGCRSInstall/ATGCRSInstall.pdf
https://www.sparkred.com/blog/installing-oracle-commerce-11-1-with-commerce-reference-store/
*

unable to find DLFileEntryLocalServiceUtil.getFileEntryByTitle() in liferay 6.1

Is there any direct api to fetch a file entry by title with given folder id.
I have tried DynamicQueryFactoryUtil, apart from this is there anything to fetch DLFileEntries by title.
I believe DLFileEntryLocalServiceUtil.getFileEntryByTitle() is not there anymore in Liferay 6.1
In Liferay 6.1.0, I can see there is
com.liferay.portlet.documentlibrary.service.DLFileEntryLocalServiceUtil.getFileEntryByName(groupId, folderId, name), as I get from lib/ext/portal-service.jar
You can also see the official documentation here
I think you start by making sure you have the correct libraries imported
EDIT:
I guess that the parent folder and groupID are needed as more than 2 DLFileEntries can have the same title/name. If you need exactly 1 result, and giving only 1 attribute, you can use getDLFileEntry(long fileEntryId). If this doesn't help either, you should tell us some more on what you want to do , and what information you have available (except the title of course)
Liferay has a strange compatibility policy.
Seems like they renamed the getFileEntry to getFileEntryByName and getFileEntryByTitle to getFileEntry. The old and new getFileEntry both share the same singature, but the parameter name is different. :-(

SugarCRM CE smarty error after upgrade

I recently upgraded our SugarCRM CE form 5.x to 6.2.6. I had some uphill experience but I overcome everything except one issue.
The following error appears in the "Email Address" area on Contact, Opportunity and other similar pages.
Warning: Smarty error: unable to read resource:
"include/SugarFields/Fields/Base/detailViewFunction.tpl" in
/home/campusre/public_html/sugar/include/Smarty/Smarty.class.php on
line 1095
I did a search on SugarCRM forum and I found only one similar thread that was old and not answered. I also contacted our hosting company to check if this problem is related with the file or folder permission but they confirmed that it is not the problem in this case.
I am a developer but didn't do any SugarCRM and Smarty development before. I am investigating the code by my self but without success so far.
Any suggestion will be highly appreciated.
Thanks in advance.
unable to read resource: include/SugarFields/Fields/Base/detailViewFunction.tpl
This usually means that incorrect permissions are set on this file or that the file doesn't exist. However, in this case it looks like a casing issue. The file is actual camel case and named DetailViewFunction.tpl. It looks like you are running into a case-sensitive issue. My initial guess is that it is due to an old module or piece of code from 5.x.