I was looking for an answer to this question through Google and the site but did not find the right answer.
The system opencart attribute whether it is possible to set values in an image?
version opencart - 2.1.0.2 (rs.1)
more:
I wanted to download the products via the file .xls. To do this, I installed the module export / import .xls. structure file:
Here, a column with a red background is an attribute, it must be the values of the image. This file shows the image link. Now, how can I upload the product up correctly with this file?
this is a readme.txt :
Export/Import Tool (V2.19) for OpenCart 2.0.x
=============================================
The Import/Export Tool allows the admin user to do a bulk export
of categories, products, options and attributes to an Excel spreadsheet file.
The spreadsheet file can be edited offline and then be re-imported to the OpenCart database.
New features include:
The Import can be incremental, that is, data is updated or added to the OpenCart server.
Or it can be non-incremental which means all old data is first deleted before the Import.
The Export can be limited to certain data ranges only for products and categories.
Multiple languages are now supported, too.
Requirements and Limitations
============================
Memory requirements can be quite high.
Not every shared web hosting account supports a high process memory usage.
Therefore, if you use a basic shared web hosting account,
no more than a few thousand products can be exported or imported at a time.
Use a more dedicated web hosting account if a higher number of products
are to be processed in one go. Or export and import multiple times in smaller batches.
Installation
============
In the OpenCart admin backend, do the following steps:
Step 1)
Go to Extensions > Extension Installer
Step 2)
Upload the opencart-2-0-0-x-export-import-multilingual-2-xx.ocmod.zip
Step 3)
Go to Extensions > Modifications
You should see any entry for this Export/Import tool
Step 4)
Click on the Refresh button (top right of the page)
Step 5)
Go to System > Users > User Group > Edit Administrator
Step 6)
Set access and modify permissions for 'tool/export_import'
That's it!
If during the install you get an error saying "Could not connect as ......"
while uploading this zipped extension via the Extension Installer,
you probably have the FTP support disabled from your hosting.
In that case you may try the following OpenCart Extension Installer fix first:
<http://www.opencart.com/index.php?route=extension/extension/info&extension_id=18892>
Further help and customized versions
====================================
This tool has been successfully tested for a standard OpenCart 2.0.x.
Don't use other Opencart versions with this module.
If you need a customized version of the Export/Import Tool,
let us know and we can create one for a charge.
You can contact us at <http://www.mhccorp.com>
Related
This question is answered with "it contains assets for the preview canvas", which isn't enough information.
Does the preview assets folder give me any additional power over the preview canvas? If so, how can I utilize it?
Does the preview assets folder give me any additional power over the preview canvas? If so, how can I utilize it?
Preview Assets as it is seen below just by default registered development time only catalog of resources.
So you can store there any images, colors, files, ie any resources, which can be used in Preview Canvas only, for testing purpose. In example to not download one from internet, cloud, or fetch from database. Because Preview is for fast UI-only look & test, so data source is not important, so to test & tune UI you don't need to fetch external data but use locally stored test data.
You can add/name any other development time asset/folder in there as well.
Trying to use the info in:
http://docs.ckan.org/en/ckan-1.4.3/authorization.html
to create users and assign roles to specifics package and the command right not working.
For instance:
paster --plugin=ckan rights -c /etc/ckan/default/development.ini list
I get error:
Command 'rights' not known (you may need to run setup.py egg_info)
Known commands:
celeryd Celery daemon [DEPRECATED]
check-po-files Check po files for common mistakes
color Create or remove a color scheme.
config-tool Tool for editing options in a CKAN config file
create Create the file layout for a Python distribution
create-test-data Create test data in the database.
datapusher Perform commands in the datapusher
dataset Manage datasets
datastore Perform commands to set up the datastore
db Perform various tasks on the database.
exe Run #! executable files
front-end-build Creates and minifies css and JavaScript files
help Display help
jobs Manage background jobs
less Compile all root less documents into their CSS counterparts
make-config Install a package and create a fresh config file/directory
minify Create minified versions of the given Javascript and CSS files.
notify Send out modification notifications.
plugin-info Provide info on installed plugins.
points Show information about entry points
post Run a request for the described application
profile Code speed profiler
ratings Manage the ratings stored in the db
rdf-export Export active datasets as RDF
request Run a request for the described application
search-index Creates a search index for all datasets
serve Serve the described application
setup-app Setup an application, given a config file
sysadmin Gives sysadmin rights to a named user
tracking Update tracking statistics
trans Translation helper functions
user Manage users
views Manage resource views.
but if I create a user like this:
paster sysadmin add seanh -c /etc/ckan/default/development.ini
works ok, so I don't think the problem was in my enviroment.
Note:
Centos 7.4
ckan 2.7.3
thanks
'Rights' was deprecated in the migration to CKAN 2.X, and the paster command removed.
From CKAN 2.0, permissions are organization by organization and by group. It's a simplification, catering for what is considered the most common use case.
However if you need to control user permissions on a single dataset (rather than all the datasets in an org/group together) then that dataset needs to be on its own in a org or group. Or you can customize the auth system using IAuthFunctions.
We have a website featuring Sitecore 8.1 with multiple content editors. Is there any way to log their activity, as in listing the actions they have performed in terms of editing/publishing/unpublishing?
We had a problem last week which I suspect being caused by someone unpublishing the wrong item, but I need to make sure this is the case, or at least I would like this ability in the future.
Do I need to create my own event-triggered logging?
There's nothing fully out of the box to provide those reports in Sitecore. You can take a look at the Sitecore Audit Trail module which will log all the "editor action" audit information into a separate log4net appender. You can find more information on the module in this blog post, but note that the module is only mark as compatible to Sitecore 7.5, it should not be hard to make this work with Sitecore 8.1, namely updating the appender config since the log4net config is now within the <sitecore> node in config.
Sitecore does log content editor actions out of the box in the normal log files (in Data\logs), they start with "AUDIT" so you can find them. It logs things such as items being saved, publishes starting, etc. Do a search in the log files to find them.
You can get these saved to a separate log file for easier review: https://sdn.sitecore.net/scrapbook/how%20to%20make%20sitecore%206%20write%20audit%20log%20to%20its%20own%20file.aspx
This still works in Sitecore 8 except the setting is in App_Config/Sitecore.config now.
You can use Sitecore Advanced System Reporter
Sitecore 6 ships with a very useful function called My Locked Items. At times, though, admin users may want to see all locked items, not just those locked by them. I wrote a little application to do just that. Then I thought of making it more generic, so that one could create other type of reports easily. The result is a little framework which allows to create many types of reports in very short time. In this module I provide this framework together with many useful example reports like:
items modified updated in the last X days
items that have more than X children
items that are publishable but either do not exist or have a different version in the web
database.
items that are based on a particular template
items with validation errors
which templates have been linked to a workflow
locked items
publishable items with broken links
audit information
errors in the log files
items that have stayed in the same workflow state for more than X days
and more.
You can now also parametrise those reports, save them as links in the desktop, export them, or even create a scheduled task that emails some of them automatically. In addition, you can also apply commands to the items reported.
You can download the module from : https://marketplace.sitecore.net/en/Modules/A/Advanced_System_Reporter.aspx
Module is available for Sitecore 6.4 to 8. I don't know if has the functionality you look but you can customize it.
You can check this blogpost how to extend it: http://www.seanholmesby.com/sitecore-auditing-with-the-advanced-system-reporter/
Update
Install the module
Run the module and choose reports like in picture.
Run the report
View the report or export it like csv, excel or xml .
I am working on a SP2013 project for a customer, and I need to set up a working environment for development, testing and production. Let's assume for the sake of simplicity that the work consists only of various customizations (lists, libraries, apps, themes etc.) and no code.
My setup is as follows:
The production environment is on some servers on the customer site
The test environment is set up in Azure
The development environment is on a virtual machine on my PC
Now, let's assume everything is set up correctly on each environment, and I want to be able to support the following tasks:
I do customizations on my dev environment, and want to deploy this in test for others to test, prefereably with existing data
After testing and QA, I want to deploy from test to production. This must of course only affect customizations, not existing data
Every now and then I would like to take a snapshot of the production environment and move it to test, so that the deployment of a new feature from development can be done as realistic as possible
I want to perform these tasks as smoothly and efficiently as possible, especially when deploying from dev to test which is done often. Deploying from test to production will not be done that often, and hence some more manual work will be tolerated.
I know of a few mechanisms that might be relevant:
Content deployment
Cross site publishing
Content database backup/restore
Save site as template, export wsp and import
(Last resort) Manually set up each customization by hand
Could some of you experienced SharePoint devs/admins make some recommendations as to which mechanism to use in which situation, when to not use it etc.? Are there other methods that should be mentioned? Remember that the three environments reside in separated physical environments, which will probably make a fully automated solution difficult. Would it make it easier if I set up the test environment on the customer site (i.e. part of the same farm)?
Another option depending on your specific customisations might be a third party tool. There are a number of them out there. ShareGate is one I have personally been using for migration work and seems very simple and effective for moving content around quickly between environments. Attunity Repliweb for SharePoint is another that might be worth looking at for the sort of development specific release work that you require.
As for native options, I am still finding my way as well but here are my suggestions :
Where possible I have used Visual Studio to create solution packages containing features to deploy pieces of functionality. A branding solution package for example might include several features that deploy your custom master pages, theme / look files, common JavaScript libraries and images.
Feature deployment makes it easy for you to deploy or remove functionality between environments and to reuse functionality between sites. Additionally you can add your Visual Studio solutions to a source control system such as VS Online or GitHub.
For one off sites I have created a dev site, configured it then used the built in SharePoint backup and restore to deploy it to prod. Subsequent changes have been created in dev and then manually applied to test and prod. Depending on the customisations this has been quite time consuming. You might combine this with a tool such as ShareGate to automate the deployment of individual artifacts such as a customized list from one environment to another.
For moving content around I have been using a combination of ShareGate for things such as documents alongside Boost Solutions Excel Import for handling list data. This allows me to export large amounts of list data to excel and easily reimport it into a new list which might be a copy that I have added new functionality to in preparation for replacing the old prod list or perhaps dev / test lists that I am populating before doing a full site backup to restore to production.
Good luck and hopefully some of these suggestions are useful to you ! I will be following this question as I am also interested to hear of better methods / habits for managing the SharePoint development cycle.
I finished setting up a development environment for a SharePoint 2013 production environment that I maintain. The last step was to move my production content to my development environment. I had to dig around a bit to find the PowerShell etc. Rather than go through that again next time, I decided to write a blog about it, so that I’d have all the steps in one place.
The first step is to back up the content database that you want to restore to development. To do this open up SQL Server Management Studio, right-click on the database you want to back up, hover over tasks, and select backup. You will be presented with the Back Up Database window. Make sure that your backup type is set to full, give the backup a name or stick with the default, and note or change the destination.
You can skip these steps if you have scheduled backups running and are able to access the backup drive. In that case just go grab a copy of the most recent full backup and copy it to your development SQL Server.
The next step is to restore the database to development. To do this open up SQL Server Management Studio in your development environment, right-click on the Databases folder, and select Restore Database. When presented with the Restore Database window, click on the Device Radio Button and click the ellipsis next to the text box. This will bring up the Select backup devices window. From there click Add, locate your backup file and click OK, click OK again to be returned to the Restore Database Window, and finally from there click OK. Now your database has been restored, and you are ready to add it to SharePoint.
If you don’t already have one with content in it that you don’t care about in it, create a new Web Application…
https://sharepointv15.wordpress.com/2012/07/24/create-a-web-application-in-sharepoint-2013/
Don’t worry about creating a site collection.
Now go to Central Admin and click on Manage content databases under Application Management.
rsd1
Make sure that the correct Web Application is selected. If it is not click on the drop down arrow next to the Web Application name, click change web application and select the correct Web Application in the window that you are presented with.
rsd2
Next click on the Content Database name
On the Manage Content Database Settings screen scroll down, click on the Remove Content Database check box, click OK on the warning pop up and click OK at the bottom of the screen.
rsd3
Now you’ll need to open up the SharePoint 2013 Management Shell as an administrator. To do this click on your start menu, click all programs, click on the Sharepoint 2013 folder, right-click the SharePoint 2013 Management Shell and select Run as Administrator.
From here you will run the Mount-SPContentDatabase cmdlet
Mount-SPContentDatabase “MyDatabase” -DatabaseServer “MyServer” -WebApplication http://sitename
Click below for details on this cmdlt…
http://technet.microsoft.com/en-us/library/ff607581.aspx
At this point you should be able to navigate to the web application URL and see the Site Collection that lives in the database you just mounted.
Note: This will work in SharePoint 2010 or SharePoint 2013. However, the database must be the same version of SharePoint that the farm you are trying to mount to is. If it is a lower version it will automatically try to upgrade it, so keep that in mind.
follow the below link.
https://sharepointv15.wordpress.com/2013/03/21/moving-content-between-environments/
Please help me how to copy a page from the existing application of Apex to another work space of Apex application.
You can't do this out of the box.
Beside workspace ids, the application id also matters. If you have 2 different workspaces and the same application in it but with different IDs, this further complicates things.
What you could always do is export the complete application, import it but use a different id so you don't overwrite the existing one, and then create a new page as a copy of the newly imported application's page.
Antoher way would be to edit the exported PAGE SQL file but, let me stress this, this is not recommended. And as so graciously stated in the OTN forums now and again, if you'd require support with an application/apex issue and they would find you were messing around in the sql files you'd not get support there. Only do this when you UNDERSTAND and KNOW what you're about to do! If you alter the code without understanding what you are doing you could be in a far worse situation than the one you started in. Any other case, follow the application export/import/copy line.
Anyway, I was in a position where workspace IDs differed but application IDs not. In this case altering the exported file is quite trivial and requires editing only 1 (one) line and concerns this piece of code:
begin
-- Assumes you are running the script connected to SQL*Plus as the Oracle user APEX_040200 or as the owner (parsing schema) of the application.
wwv_flow_api.set_security_group_id(p_security_group_id=>nvl(wwv_flow_application_install.get_workspace_id,27000294100083787867));
end;
/
This is one of the first pieces of code in the exported page file. As you can see, the workspace ID is set here. If attempted to be imported into an application (even if the app id matches the one you're trying to import to) you'd get an error. Change the ID to the one matching the workspace however and it'll work. Of course, you need to know the workspace IDs, and you can find these by executing this select on your apex environment(s?)
select workspace, workspace_display_name, workspace_id from apex_workspaces
Some good advice:
If you're still in the start-up phase of your apex installation, you might want to make sure that your workspace ids are identical. For example, with a test and production environment having identical workspace and application ids is very interesting. You'd have 2 instances (2 database installations on 2 different servers), but want the IDs to be the same.
To make sure of this, you can EXPORT the workspace from one environment and then IMPORT it into the other one. You can do that from the instance administration in apex, ie the internal workspace.
This is now supported in APEX version 4.2 - per Oracle doc...
7.3.4 Copying a Database Application Page
You can copy a page from the current application or from another application. During the copy process, you can also copy shared components or change mappings to shared components in the target application.
To copy a page:
Navigate to the application you want to copy to:
Navigate to the Workspace home page.
Click the Application Builder icon.
Select an application.
Select a page.
The Page Definition appears.
In Tree view:
Under Page Rendering, select the page name.
Right-click and select copy.
In Component view:
Under Page, click the Copy icon.
For Copy Page Option, select one of the following:
Page in this application
Page in another application
Follow the on-screen instructions.
In APEX 4.0 to copy a page from any Application:
Edit any page in your Application
Hit the Create▼ button
Choose New page as a copy