I have an article class document in Latex.
I want the figure numbering to just be counting within the section. 1.1, 1.2, 1.3 etc. for figures within subsection and not 1.1.1, 1.2.1, 1.2.2,...
I tried
\renewcommand{\thefigure}{\arabic{section}.\arabic{figure}}
\counterwithin{figure}{section}
\renewcommand{\thefigure}{\arabic{subsection}.\arabic{figure}}
\counterwithin{figure}{subsection}
and just
\renewcommand{\thefigure}{\arabic{section}.\arabic{figure}}
\counterwithin{figure}{section}
but then the figure count reset so it becomes 2.1, 2.1, 2.2, for every new subsection.
Thanks
Related
I am facing problem with tt_news in typo3 version 6.2.11.
I can not set date above 2020 year. I can set till 31.12.2020 and after that all dates are disabled.
I have taken 2 screenshot of it. Any hint or solution would help me.
Thanks
enter image description here
tt_news has a hardcoded maximum for the end date, which in the version you're using is 31-12-2020. The best advice is to upgrade. TYPO3 6.2 isn't supported anymore.
However, if you need a quick fix, you'll need to change it in the TCA file of tt_news. You can find that in typo3conf/ext/tt_news/tca.php or typo3conf/ext/tt_news/Configuration/TCA/tt_news.php depending on which version of the extension you're using.
This file contains an array with the configuration of the fields for this table. For the field endtime it should contain something like this:
'range' => [
'upper' => mktime(0, 0, 0, 31, 12, 2020)
]
You'll need to change that date.
The range-array occurs twice in tca.php. The first occurrence should be updated
$TCA['tt_news']['columns']['endtime']['config']['range']['upper']
At the next one you can do as well
$TCA['tt_news_cat']['columns']['endtime']['config']['range']['upper']
My fault was to change the latter one without effect.
I updated a typo3 site from version 6 to version 7 and now to version 8 heading for 9 or 10. Now some contents on my page are missing. When I look in the page editor all elements have errors like [INVALID VALUE ('ce_head-image')] or [INVALID VALUE ('ce_product')]. What does this mean?
Your content elements (CEs) have no rendering definition.
the rendering definition can be missing because of:
the basic rendering extension is missing
EXT:CSC leaves the core and is an TER extension
the names of the CEs is changed inside the basic rendering extension (there should be an upgrade wizard)
the same for CE types defined by additional extensions
extension is no longer supported for the newer TYPO3 version
changed names in newer versions (upgrade wizard?)
the registering of additional CEs does not work any longer as it has been changed in the core
As the names you have sounds unfamiliar my firsst guess would be the last reason.
I've got a simple task at hand: to plot integer-integer value pairs using line chart or XY chart or whatever using bean type of datasource. The bean in question returns long value both for X and Y axis. The default behavior one would expect is to show ticks of 1, 2, 3, 4, etc. on both axis.
But no, I get values like 2.5 or 1E1 for the same application running on two different machines! OK, this old post suggests to set tickLabelMask to "#". Now integers are indeed displayed, but with repeating values, like 0, 0, 1, 2, 2, 3, 3, 3, 3, 4, 4, etc. The same post suggests I add two properties to my report,
net.sf.jasperreports.chart.domain.axis.tick.interval
net.sf.jasperreports.chart.range.axis.tick.interval
Unfortunately, these have no effect when added at report level in JRXML file. When I try to add them at chart level between <reportElement ..> tags, Jaspersoft Studio removes them once I save the file. So, I take it , something has changed.
So, how could I fix this issue?
I'm using Jaspersoft Studio 6.9.0 and Jasperreports 6.6.0
Nowadays it's done using "Chart customizers". General info can be found here. To put it short, in design view select the chart, go to Properties window, select "Chart" there, scroll down to "Chart customizers" section, click "Add", and the choose range and tick customizer.
Additional artifact must be included into your project: jasperreports-chart-customizers
During creation of new elements in EA i tried to set the element position using Element.TreePos but after setting this still the element in EA is getting inserted based on the Alphabetical order. But once the project is reloaded it is getting arranged properly as per the TreePos.
EA.Element mobjElement= mobjParentelement.AddNew("","Requirement");
mobjElement.Name= "Sample";
mobjElement.TreePos=1;
mobjElement.Update();
You have to reload before a change in TreePos becomes apparent.
You can use EA.Repository.RefreshModelView(long PackageID). According to the documentation the PackageID parameter should limit the reload to only the package with the given ID, but I have not found a difference between reloading a single package or reloading the whole model (using 0 as parameter).
Since v13 there is also EA.Repository.ReloadPackage(long PackageID) which might do what you need, but I haven't tested that myself. From the documentation it is not clear what the exact difference is between the two operations.
Since updating from Flux 6.0.2 to the newest Flux TER-Release (7.0.0) I have the problem that all my defined flux:field.select items are switched. I have them defined as an array like this items="{0: {0: 'value shown as a CSS class in the frontend',1: 'value shown in BE'},}". But now I get the BE value in the frontend template.
Also all my content elements from my provider extension are shown twice (without a title) in the backend and the fields defined in the 'Configuration' section of my content element are shown twice.
There's also a RTE field shown at the bottom of my content element that has not been there before.
BE Output: view
Code on Pastebin: http://pastebin.com/CNcphn2k
Any help deeply appreciated.
EDIT:
I just set up a fresh instance of TYPO3 6.1.9 (blank package) and installed my extension with the above mentioned content elements. Dependencies were resolved automatically as it should (newest versions). Via the content wizard I tried to create a new element and I get the same result as in my existing install I first noticed this bug in.
EDIT2:
I was able to narrow it down to the flux:form.container tag. This duplicates the output in the BE. The select values are still switched though.
It is possible that you missed this official announcement:
http://fluidtypo3.org/blog/news/new-colpos-value.html
Failure to run the update script before letting TYPO3 change the type of the colPos value will result in the symptoms you describe. There is, unfortunately, no way to restore this (since your SQL will have cropped off all negative values and made them zero without any backup).
Restore from a backup and run the script and you should be fine.