Search Results for 'bakery'

Results from the Forum
sprouteemeg
tagDiv Member

Hi CrunchCommish,

You got it. The directions do say to use either WP BAkery or TagDiv Composer. I only found that on second reading after support helped me. Glad you figured it out.

lastwordonsports
Participant
#0

First problem: Why are you trying to write to files inside the Plugin folder? wp-content/uploads is usually web-writeable on WordPress, whereas folders in themes and plugins should NOT be web writeable, for security reasons. When I unlock our site, the error message goes away.

As a WordPress developer (plugin, theme and core WP) absolutely dialed in on securing and hardening WordPress, I am dismayed that you want to create these files inside the plugin folder.

Warning: fopen(plugins/td-composer/includes/templates/font-awesome.php): failed to open stream: Permission denied in plugins/td-composer/includes/tdc_main.php on line 902
Warning: fopen(plugins/td-composer/includes/templates/typicons.php): failed to open stream: Permission denied in plugins/td-composer/includes/tdc_main.php on line 902
Warning: fopen(plugins/td-composer/includes/templates/open-iconic.php): failed to open stream: Permission denied in plugins/td-composer/includes/tdc_main.php on line 902
Warning: fopen(plugins/td-composer/includes/templates/td-multipurpose.php): failed to open stream: Permission denied in plugins/td-composer/includes/tdc_main.php on line 902

Second, we run tagDiv Composer on a *very* large MultiSite network (24 sites, 50+ gigs of content in wp-content/uploads). When we unlock the site (see first issue), tagDiv Editor just sits there and hour-glasses all day long. We have no issues with this on single standalone sites. Health Check is below the image…

tagDiv Composer does nothing...

`
### wp-core ###

version: 5.2.2
site_language: en_US
user_language: en_US
permalink: /%year%/%monthnum%/%day%/%postname%/
https_status: true
user_registration: false
default_comment_status: open
multisite: true
user_count: 3195
site_count: 24
network_count: 1
dotorg_communication: true

### wp-dropins (1) ###

sunrise.php: true

### wp-active-theme ###

name: LWOS Newspaper
version: 1.9.8
author: tagDiv
author_website: http://themeforest.net/user/tagDiv/portfolio
parent_theme: Newspaper
theme_features: post-formats, post-thumbnails, automatic-feed-links, html5, woocommerce, bbpress, align-wide, align-full, editor-font-sizes, editor-style, menus, widgets
theme_path: [REMOVED]/ms.lastwordonsports.com/wp-content/themes/Newspaper

### wp-themes (2) ###

Newspaper: version: 9.8, author: tagDiv
Twenty Sixteen: version: 2.0, author: the WordPress team

### wp-plugins-active (29) ###

Advanced Database Cleaner: version: 2.0.0, author: Younes JFR.
Akismet Anti-Spam: version: 4.1.2, author: Automattic
Broadcast: version: 44.02, author: edward_plainview
Classic Editor: version: 1.5, author: WordPress Contributors
Edit Flow: version: 0.9, author: Daniel Bachhuber, Scott Bressler, Mohammad Jangda, Automattic, and others
Email Users: version: 4.8.8, author: Mike Walsh & MarvinLabs
Force ReAuthentication: version: 1.3.1, author: Shrkey
Google Analytics Dashboard for WP (GADWP): version: 5.3.8, author: ExactMetrics
Head, Footer and Post Injections: version: 3.1.3, author: Stefano Lissa
Multisite Enhancements: version: 1.5.1, author: Frank BĂŒltge
Multisite User Role Manager: version: 1.0.7, author: OzTheGreat (WPArtisan)
NextScripts: SNAP Pro Upgrade Helper: version: 1.5.9, author: NextScripts
NextScripts: Social Networks Auto-Poster: version: 4.3.8, author: NextScripts
Regenerate Thumbnails: version: 3.1.1, author: Alex Mills (Viper007Bond)
Richweb WP Lockdown: version: 2.6.5, author: Jordan Burch, Jacob Dunn & Doug Hazard
RSS Multi Importer: version: 3.15, author: Allen Weiss
tagDiv Cloud Library: version: 1.3, author: tagDiv
tagDiv Composer: version: 2.4, author: tagDiv
Unfiltered MU: version: 1.3.1, author: Automattic
User Role Editor: version: 4.51.2, author: Vladimir Garagulya
WordPress MU Domain Mapping: version: 0.5.5.1, author: Donncha O Caoimh
WP Crontrol: version: 1.7.1, author: John Blackbourn & crontributors
WP Dashboard Notes: version: 1.0.9, author: Jeroen Sormani
WPForms: version: 1.4.5.2, author: WPForms
WPForms Custom Captcha: version: 1.1.1, author: WPForms
WP Last Login: version: 2, author: Konstantin Obenland
WP Rollback: version: 1.6, author: Impress.org
Yoast SEO: version: 11.8, author: Team Yoast
Yoast SEO: News: version: 9.2, author: Team Yoast

### wp-plugins-inactive (2) ###

tagDiv Social Counter: version: 4.6, author: tagDiv
WPBakery Page Builder: version: 6.0.5, author: Michael M – WPBakery.com

### wp-media ###

image_editor: WP_Image_Editor_Imagick
imagick_module_version: 1673
imagemagick_version: ImageMagick 6.8.9-9 Q16 i586 2019-05-14 http://www.imagemagick.org
imagick_limits:
imagick::RESOURCETYPE_AREA:
imagick::RESOURCETYPE_DISK: -1
imagick::RESOURCETYPE_FILE: 6144
imagick::RESOURCETYPE_MAP:
imagick::RESOURCETYPE_MEMORY: 2 GB
imagick::RESOURCETYPE_THREAD: 10
gd_version: 2.1.1-dev
ghostscript_version: 9.26

### wp-server ###

server_architecture: Linux 3.16.0-8-686-pae i686
httpd_software: Apache
php_version: 5.6.40-0+deb8u4
php_sapi: apache2handler
max_input_variables: 1500
time_limit: 90
memory_limit: 300M
max_input_time: 20
upload_max_size: 72M
php_post_max_size: 72M
curl_version: 7.38.0 OpenSSL/1.0.1t
suhosin: false
imagick_availability: true
htaccess_extra_rules: true

### wp-database ###

extension: mysqli
server_version: 5.5.5-10.2.19-MariaDB-log
client_version: 5.5.62

### wp-constants ###
WP_HOME: undefined
WP_SITEURL: undefined
WP_CONTENT_DIR: [REMOVED]/ms.lastwordonsports.com/wp-content
WP_PLUGIN_DIR: [REMOVED]/ms.lastwordonsports.com/wp-content/plugins
WP_MAX_MEMORY_LIMIT: 300M
WP_DEBUG: false
WP_DEBUG_DISPLAY: true
WP_DEBUG_LOG: false
SCRIPT_DEBUG: false
WP_CACHE: false
CONCATENATE_SCRIPTS: undefined
COMPRESS_SCRIPTS: undefined
COMPRESS_CSS: undefined
WP_LOCAL_DEV: undefined

### wp-filesystem ###
wordpress: not writable (This is our security plugin, protecting the site)
wp-content: not writable (This is our security plugin, protecting the site)
uploads: writable
plugins: not writable (This is our security plugin, protecting the site)
themes: not writable (This is our security plugin, protecting the site)

CrunchCommish
tagDiv Member

update. I disabled WPBakery Page Builder and it now works.

Oceane237
tagDiv Member

Thank you Vlad! Deactivating WP Bakery fixed the issue.

Vlad S
tagDiv Staff

Hello !

Please try deactivating WP Bakery and check again. Let me know if this fixed your issue !

Thank you !

LG
tagDiv Member

Hi Vlad,

Ok, after much head scratching and page testing, there is definitely something wrong with my theme.

1) Even if I import a page or section template in tagDiv Composer and do nothing to it, except save and view. None of the rows will display as full width. This is the case in Composer and the page itself.

2) I created a new footer page, using an imported template with a similar layout to my own (1 row/3 columns for the footer, 1 row/2 columns for the sub-footer). I did nothing to it, except set the sub-footer menu and reduce the font size.
– The result: in tagDiv Composer, the columns are stacked in both the footer and sub-footer and neither row shows as stretched. When viewed in situ on a page, the rows and columns behave as they should and align horizontally. Small win…
– For some reason, the last couple of days the import feature isn’t working properly either. When I click the button to import, the confirmation box appears behind the import modal – the only way to click OK is to add display:none to the modal via Chrome Dev Tools.

3) Unfortunately, #2 only works with pages created using tagDiv Composer and WPBakery. Any pages created using Gutenberg, seem to break the footer CSS. The page structure (for the footer section/page) is the same, but some of the same CSS is being overwritten, as it appears to come after in order of specificity. In Chrome Dev Tool, the ‘winning’ styles appear above the ones being overwritten.
– In pages created using tagDiv Composer or WPBakery, I still can’t get any rows to stretch no matter what I do (believe me, I’ve tried!).
– The only way to get stretched rows of any kind, is to build pages using Gutenberg Blocks and plugins. Which is why all of my pages are showing a broken footer, because I had to go back to basics as the other 2 methods are currently unusable.

The solution:
#ti-copyright-footer .td-pb-span6 { width: 50% !important; }

I’ve added the code to the Live CSS window for the footer page and given the row an id, so it won’t conflict with anything else (hopefully). It feels like a bit of a hack, as I’m not a developer and generally wouldn’t mess with the structure of a page, for fear it’ll mess up it’s responsiveness (media queries, etc). I haven’t tested that yet, but it’s nearly 1am, so that’s it for now…

I’m hoping this level of detail might give you a better idea of what’s going on, so that you can help me resolve it properly. I’m not convinced that’s the best fix (it was way too easy), unless you can confirm it won’t effect anything else on the site. Or perhaps you can come up with a cross device/cross platform solution?

Many thanks.

keithkhoo
tagDiv Member

Calin, you’re right, I deactivated WPBakery and the layout is fixed now.
Thanks for your help!

Calin
tagDiv Staff

Hi,

I think that is is happen because f the WPBakery plugin.
Please make sure that you don’t have a plugin conflict, please deactivate all non theme plugins and let only those that have the “tagDiv” text in name, after that make sure that all cache is clear and try again.

Thank you!

Calin
tagDiv Staff

Hi,

What I said is that using flex blocks from tagDiv Composer not WPBakery you can set the layout for each device -> http://prntscr.com/opf5vx -> http://prntscr.com/opf6lf so you do not design a completely different website, you just adjust the elements from your current page on your website to adjust for all devices.

I hope that you understand what I mean.
Thank you!

Calin
tagDiv Staff

Hi,

If you want to try the update you can do it on localhost or on a sub-domain for tests, in this way you can check if the elements you need are compatible or not, in this way you’ll know if you can or not to use the update.

Unfortunately I do not know an estimate time because the new update will be about to make the theme lighter and more fast.

For the moment, from what I know the WPBakery plugin will continu to be a suported plugin in our theme.

Thank you you for your understanding!

martialwarrior
tagDiv Member

So, you are saying that I have to design a completely different website for the mobile versions of my website if I use TagDiv’s Ppage builder? I do not have to do this with WPBakery Page Builder.

LG
Participant
#0

Hi,

I can’t seem to make head nor tail of tagDiv Composer… I understand you’re supposed to be able to create full width rows using it, but for some reason I can’t get it to work properly. I’ve tried the different ‘stretch row’ settings, but it won’t stretch beyond the width of the site. I thought I’d try WPBakery, but I get the same result – I can set the setting, but it doesn’t make a difference in the Composer view or on the live pages. The only way I can get a full width row, is via the Gutenberg Blocks Builder, using a plugin.

I did manage to create a full width footer page, which I’ve set via the Theme panel. The only way I could get this to work as full width, was to import and customise one of the footer templates. It shows as full width on pages, but still doesn’t show as full width in tagDiv Composer. Not a problem, as long as it displays correctly. However, as of yesterday, the sub-footer (1 row, 2 columns, aligned left and right) is now displaying as 2 rows stacked – it’s overriding the .td-pb-span6 (50%) setting. I looked at the footer page in tagDiv Composer yesterday (when trying to replicate the stretch settings), but didn’t change anything or re-save it. The footer/sub-footer display correctly in composer, so have no idea why it’s showing as broken on all pages…except one.

I tried re-saving the footer page (without making any changes), but that hasn’t made any difference and I can’t see anything special about the one page where the sub-footer is showing correctly – even the sample page which came with the theme and that I haven’t touch, is showing the broken sub-footer now. To confuse things further, having re-saved the footer page and it making no difference to existing pages, I created a new page in tagDiv Composer (just a client, inline text and a couple of empty space elements), just to see the result. NOW the sub-footer in Composer is broken, but displays fine on the actual page…

What’s going on?? 🙁 Unfortunately I can’t share a live link, as I’m working locally, but if you tell me what info you need, I should be able to find it and report back/provide a screen grab.

Many thanks in advance!

Calin
tagDiv Staff

Hi,

There were some fix made for a better compatibility between those two builders, but in the last version ( Newspaper v9.8 ) is better to use only one, so if you want to use tagDiv Composer, do not activate the WP Bakery, if you want to use the WP Bakery let the TagDiv Composer activate only for the theme functionality, a mix between those two can provide some errors.

Thank you for your understanding!

isagachie
Participant
#0

Hi! I administrate 5 sites under Newspaper (and intend to build 2 in very near future) but I encoutered some annoying issues recently with a 9.7.2 version (I think you remember 🙂 and thanks again for your help!) and I’m bit anxious about updating all my sites and well… buying new licences.

Can you tell me if these issues have been resolved now with 9.8 and by providing a more recent version of WPBakery Page Builder?
– As soon as I used (the really great) Header Composer, all pages structure created with WPBakery were messy. And I’ve been obliged to recreate all my pages using TagDiv Composer (wich doesn’t always fits my needs, yet). So my question is… can I without any problem now mix TagDiv Header composer’s headers with Page Builder’s content components?
– corollary problem: does the issue appearing in a two menus header, were first sub-menus appearing “under” the second menu (letting sub-menus unclickable) is now resolved without needing to add custom CSS?

dillonwalsh
Participant
#0

Hi. Love your theme and have 4 licenses. I have the most updated version (9.8) and all my WordPress, plugins, etc., are all up-to-date. I also have Ultimate Addons for WPBakery Page Builder. However, when I try to create a row of Vertical Parallax on Scroll, neither does my image appear nor does the text scroll.

When I deactivate the Newspaper theme, it works. I’ve also used the plugin developer’s sandbox and created the same element configuration there, and it works in the sandbox. But as soon as I activate Newspaper, the element no longer works.

So, apparently, the Newspaper theme is competing. Is there any way we can work around this? I love Newspaper and I love the ability to Vertical Parallax on Scroll.

pmerch
tagDiv Member

Hi Calin

1)all settings ok, all “green lights” in the System Status panel on the theme

2) I worked through all my plugins… and did in fact find that the “WP Editor” DID work if i deactivated the “Nexgen Gallery” plugin

This plugin is very popular, and I mention it here in case it helps anyone else. I’ve used that Plugin for years, before I used the Newspaper theme in fact! There were no issues with the previous versions of the theme – when using the WPBakery page builder.

Is this conflict something you can look at please? Has it already been reported – it is a massively popular plugin!

Thanks

pmerch
Participant
#0

Hi
I recently updated my newspaper theme… and had previous pages built in the old WPBakery builder, which I have now deactivated
I am trying to create a brand new fresh page using the Tag Div Composer.

I am struggling to add actual content!
I’m using a “Text with Title” block, but when I click on “EDIT CONTENT” a “WP Editor” dialogue pops up, but just hangs, showing a sort of “loading” graphic of a circle spinning round.

Any ideas? Thanks

System summary:
Theme version 9.8
PHP 7.2.20
WP Version 5.2.2
WP Memory Limit 256 Mb

shazza
Participant
#0

I get this following error when trying to change the default image used in tagDiv Composer after adding the “Inline single Image” element:

“Invalid data Current state has involved an issue. You could try an UNDO operation (CTRL+Z / CTRL+SHIFT+Z)”

I was attempting to change the image that tagDiv Composer used by default in this “Inline single Image” element by clicking on the small thumb of the image near top of left side of it’s settings panel.

I also tried removing the existing image first using the link for that, and then adding an image from the media library. However, this also results in the same error.

I then also tried this same thing by trying to change the default image used in the “Column Content” element, this also results in the same error.

Further, if I exit out of tagDiv Composer and edit using the Classic Editor instead and then attempt to add an image from the media library using the Add Media button it just silently fails with no errors shown. It does open the media library and I can browse/select an image, but the image just never gets placed on the page.

If I use the Backend block editor (WP Bakery Page Builder), choose and add an image element to an existing page this does indeed add an image. Why is this not working in tagDiv Composer or the Classic Editor?

However, in any of the wysiwyg html editors, like provided in a text block in WP Bakery Page Builder, using the Add Media button also fails same as in the Classic Editor.

Please help.

Giles
tagDiv Member

Thanks for the reply Vlad. I’ll look into deactivating WPBakery, but look forward to the function working – it would be really useful.

Best regards

Vlad S
tagDiv Staff

Hi,

There is a problem with it, it is the same on my end. Deactivating WPBakery seems to solve it. I will add this issue on our list and it will be investigated.

So the solution would be to deactivate WPBakery if this is possible, for the time being. Sorry for the inconvenience.

Thanks

Simion C.
tagDiv Staff

Hi,

There is a problem with it, it is the same on my end. Deactivating WPBakery seems to solve it. I will add this issue on our list and it will be investigated.

So the solution would be to deactivate WPBakery if this is possible, for the time being. Sorry for the inconvenience.

Thanks

Simion C.
tagDiv Staff

Hi,

Currently it is still the same, the widget sidebar won’t be available in the composer when WPBakery is active. However this will change in the coming theme update. The sidebar elements will be available regardless of WPBakery.

The update should be released this week from what I know. Sorry for the inconvenience, please let me know if you have more questions.

Thanks

martialwarrior
Participant
#0

Website: https://www.peopleplacesandpastimes.com/

I have three different websites using your newspaper theme. The two that are using WPBakery Page Builder look great on the desktop and on mobile devices. The website that I designed with TD Composer looks awful on mobile devices and certain things are not responsive at all and the text is huge etc. Why is this and how do I fix it.

I do not want to use the mobile theme.

mateusnds
tagDiv Member

Thank you.

Plugin WPBakery Page Builder was the problem.

Disabled and solved.

Thanks.

VoZz
Participant
#0

Hi guys,

So, I’m in the process of converting my WP Bakery pages to tagdiv composer. I couldn’t find the Widgetised sidebar. Then after some searching I found the reply below in another topic. This is a real problem. I can’t just switch from one to the other. I first have to build pages in concept before I can switch. If I turn of WP Bakery while I’m in the process, my current site breaks. If I leave it on I can’t get the widgets I need for the new pages. Is there a workaround for this?

Hi,

1/2. Some elements won’t be available in the composer if WPBakery is active. The widget sidebar and the HTML element are two of them. This was done because they may not function correctly when both composers are active. Maybe this will change, I can’t say for sure at the moment what will happen.
So as long as WPBakery is active, those elements will be removed from the composer element list can can’t be used.

3. Depends, how was it added in the page initially? try to edit the page and check if it’s still there, shouldn’t have been removed by itself.

Thanks

REPLY

Viewing 25 results - 1,301 through 1,325 (of 3,287 total)